Reasons to Start Soon
There are three very good reasons for putting an early emphasis on adopting new technical practices:
• Very rapid improvements are possible. Many of the technical practices can provide some quick wins to the team and organization. Pair programming, for example, can help cross-train programmers across more areas of the system. Introducing a continuous build process can reduce integration hassles to near zero. Other practices—test-driven development, for example—have steeper learning curves, but even these are measured in days and weeks rather than months and years.
• If the team doesn’t try new technical practices early, it might never try them. Too many Scrum teams adopt the bare minimum of Scrum and stop there, deciding ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access