A walkthrough of the product development process we have at ZenCash - a startup which aims to get your invoices paid faster.

2. The Zen of product development

3. ZenCash
"your virtual A/R team"
3

4. 4

5. 5

6. 6

7. Product development
• Scrum
• change is inevitable
• "knowledge comes from experience"
• simple to understand
• difficult to master: maximize ability to deliver
7

8. Team (1)
• product owner
• manages the product backlog
8

9. • story: concise description of functionality, understandable by everyone

10. Team (1)
• product owner
• manages the product backlog
• ensures value is delivered
10

11. Team (2)
• scrum master
• understands long term planning ("why?")
• "backlog grooming" w/ product owner
• ensures the work is understood by dev team
• part of the development team
• devops
11

12. Team (3)
• development team
• composed of developers (that's it)
• discuss technicalities of stories ("story time dev")
• implement stories
• participate in "weekly dev discussions"
12

13. Sprint
• sprint = time-box of 3 weeks in which a product increment is created
• must accomplish something ("sprint goal")
• organic acceleration (slow start, dash for the finish)
13

14. Sprint (2)
• during the sprint
• scope and priorities of stories can (and will) change
• quality does not decrease ("good enough")
• daily standup
14

15. Sprint (3)
• the end of the sprint
• sprint review (tweak product development process)
• "show 'n' tell"
15

16. The actual work
• key principle: "ownership"
• definition of "done"
• functionality implemented
• test coverage (unit, functional, manual)
• build passing
• works on the staging server
• code was reviewed by a peer
16

17. Conclusion
!
• start with something that works (Scrum, Agile, CoC)
• use other's tools to focus on your product (PivotalTracker)
• iterate and adapt
• things average out (performance, sprint duration)
• grow organically
• be positive about people :)
17

18. Keep in touch
• mircea@zencash.com
• @ShotgunDebuggin
• www.zencash.com/blog