Finished reading chapter 18 about Full-Kitting (FK).
My assessment of FK has matured throughout reading the book and have come to the conclusion that it is perhaps the single most important activity in determining the success of a project… and therein lies my dilemma…
Let me add some context:
- We are talking about FK for a MOVE
- FK done right will allow a MOVE to flow smoothly. If it isn’t done right or not done at all, it has the potential to raise many false positives when it comes to identifying the constraint. This is crucial on so many different levels. Not knowing precisely where the constraint is located and chasing down multiple false positives is the fastest recipe to descend into chaos. The importance of a good FK could not be stressed enough (IMHO).
What I would like to explore:
- The role and activity of a customer in FK when working on a MOVE within the context of a custom (bespoke), completely green field, software development project.
Taking into account the various techniques for getting good requirements from customers (event storming, user stories etc…), I feel FK is a lot more than that, and probably requires a lot more customer involvement. (If you agree, how would you do this effectively? If you don’t agree, I would be interested to know why.)
My gut feel, is that if FK is done properly throughout the course of a project it should take up a third, perhaps even half the time to complete the whole project (! yes… just a gut feel).
Without good FKs, I can easily see a project taking twice as long to complete, and if the concept of a “MOVE” is not properly understood, I would dare say, the project could (will!) take 5 to 10 times longer…
But my dilemma is …
- Explaining to a customer the importance of FK
- That a large chunk of the project costs will be due to FK
- That they will need to be actively involved
Especially if they are stuck in a “Cost Accounting” world (Maybe we don’t even discuss point 2 )