Chapter 18To Speed Up, Build with Skill
At first, when we set out to build a complete but tiny product in easy, small cycles, things will go badly. That’s normal. Let’s look at a few of the main things that can go wrong and what we can do about them. Think in terms of the style of these suggestions, not just the specifics.
Our team says: We can’t get all these features done in two weeks.
Yes, this is a common problem. Often when starting out, a team can’t deliver a fully integrated product increment in two weeks and will ask for more time. Instead of giving your team more time, I suggest giving them less. Ask your team to produce a fully integrated product increment in one week instead of two!
Chances are, they’ll figure out how to do it. ...
Get The Nature of Software Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
