Too often programmers begin coding without a clear plan of attack because we lack the tools and practice to formulate our technical ideas so others can understand them. This leads to technical debt, wasted effort, confused pair partners, and projects that frustrate business stakeholders. We believe that developers should have a implementation plan for their user stories before writing a single line of code. When development teams can plan and communicate effectively they write better, cleaner, easier to maintain code. Moreover, practicing planning allows teams to learn to make conscious architectural tradeoffs and become more effective and valuable to the business.

We’ll explain how making and clearly communicating a plan can lead to better solutions, produce cleaner code that’s easier to understand and maintain, and much more. We’ll also speak practically about tools and practices for sharing plans with your peers.