Building a software product can be complex. The pitfalls include prioritization, planning, focus, complexity, and more. We’ll discuss techniques on how to avoid or escape these pitfalls. This includes an activity that demonstrates the inherent complex nature of software development.

1. Escaping the Pitfalls of
Software Product
Development
Mike Clement
Greater Sum
mike@greatersum.com

3. Backlog Prioritization

4. User Story Mapping

7. Estimates

9. Probabilistic Forecast

10. Use past data
1
6
2
5
5
2
5
5
9

11. 0
5
10
15
20
25
30
2/6/2017 2/13/2017 2/20/2017 2/27/2017 3/6/2017 3/13/2017 3/20/2017
RemainingStories
Date
Simulated Burn Downs (first 50)

13. Complexity

14. Activity

15. 4 Rules of Simple Design

16. 4 Rules of Simple Design
• Passes All Tests
• Clear, Expressive, Consistent
• No Duplication
• Minimal

17. Finding a Rockstar Coder

23. Team-oriented Craftsmanship

24. Sustainable Software via Quality
• Automated Testing
• Test first
• Test-Driven Development
• Pair Programming
• Mob Programming
• Continuous Integration
• Continuous Deployment/Delivery

26. Too much money

30. Focus using WIP Limits

31. Stop starting, start finishing

33. Big Bang Release

34. 0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Compound Probability
0.9
0.95
0.99

35. Small Batches via
Continuous Delivery

38. Scrum == Agile

39. Agile Manifesto

42. Pitfalls
• Finding a Rockstar Coder
• Backlog
• Big Bang Release
• Too Much Money
• Estimates
• Scrum == Agile
• Complexity

43. Escape
• Team-oriented Craftsmanship
• User Story Mapping
• Small Batches/Continuous Delivery
• Focus using WIP limits or Stop starting, start finishing
• Probabilistic Forecast
• Agile Manifesto/Modern Agile
• Simple Design

44. Greater Sum
• https://www.greatersum.com
• https://www.youtube.com/channel/UCv9aSJaPZxgK6FEDLx9WFzQ