Clients Want to Be Agile...

Table of Contents

Clients Want to Be Agile…

One of the recent meetings involved establishing (by me, MS) a way to collaborate with a client (details intentionally slightly modified or omitted, though based on a real case). The client (K) said:

Client (K): This is a very serious undertaking and considerable costs are expected. To be honest, our sponsor has serious doubts about this amount and will not be able to spend it. The project is quite innovative, and it’s unclear how the market will respond…

Me (MS): That’s actually fitting because we can propose a different way of collaboration. The entire system is indeed a significant investment and quite risky, as the product may simply not catch on. Let’s look at what is the essence of the system… perhaps this will be the part that suggests what to do next.

(Several dozen minutes of joint analysis and discussion)

Me (MS): Great! So XYZ is what will attract customers; everything else is secondary. We call this the core business of this system. So let’s do this: let’s contract this first part, and for the other parts, we’ve presented rough estimates. After these works, it will become clear how accurate they are. But most importantly, after implementing the core, we will see how the market reacts, gather feedback, and then make further decisions.

Client (K): Okay. That looks quite promising. We will risk only 1/4 of the entire initial amount. Interesting, I need to discuss this with the sponsor.

(… the client is hooked, and the competition stands no chance, offering in a traditional model - meanwhile, the client’s concept has changed :))

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Related Posts

Two Structuring Meetings Patterns

As I describe in my book, it is beneficial to structure meetings (or parts of meetings) to make them more effective. Here are two examples useful for planning meetings, applicable in Scrum and adaptable to other contexts.

Read More

Meeting Deadlines at All Costs is a Mistake!

The Necessity of Deadlines

Deadlines are necessary. Whether you work in Scrum (Agile) or a waterfall-like methodology, one thing is certain: without deadlines, there is no motivation. According to Parkinson’s Law (no relation to the disease), deadlines are essential.

Read More

Building Knowledge in Teams: Main Mistakes and Strategies

Building Knowledge in Teams: Main Mistakes and Strategies

The topic of knowledge management in teams is largely overlooked by IT leaders. There is a silent assumption that it happens automatically. To some extent, it does, as programmers are accustomed to constantly learning to stay ahead. However, this is not sufficient. It’s not enough for everyone (or realistically, half) to learn individually. If the team is to be effective, cohesive and up-to-date knowledge is needed. Knowledge of new technologies or solutions holds limited value compared to this.

Read More