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

The Natural Order of Refactoring Examined Part 4: Refactoring to Patterns

The Natural Order of Refactoring Examined Part 4: Refactoring to Patterns

By following the steps outlined previously, we begin to see a more structured solution, predominantly consisting of methods grouped into classes. It’s now time to apply object-oriented principles, such as those encapsulated by the SOLID principles. We analyze the code for patterns of repetition, the need for flexibility, and code smells, and introduce design patterns where appropriate.

Read More

Case of Scope Creep - A Simple Introduction to BDD Part 4

Introduction

In the dessert of JBehave, Behaviour-Driven Development, and the calculator (yay), we present the last part of our series.

Read More

Young Manager/Team Leader! Get a Grip!

History tends to repeat itself, and this is a common tale among young managers and team leaders. A recurring, tragic mistake is the commitment to unrealistic deadlines.

Read More