Every project has a starting point. Whether called project Kick-off, Project Execution, or Sprint 0, from this basis the project begins to create and deliver value. Sprint 0 will begin the program execution – from Sprint 0, the team is ready and able to deliver business value that is usable and potentially releasable.

1. Mark Reynolds
Sprint 0 Projects
Mark Reynolds
September 2015

2. Sprint 0 Projects
Every project has a starting point.
Whether called project Kick-off, Project Execution,
or Sprint 0, from this basis the project begins to
create and deliver value.
Sprint 0 will begin the program execution – from
Sprint 0, the team is ready and able to deliver
business value that is usable and potentially
releasable.
Not everyone will agree with some of the premise.
Some will.

3. Sprint 0: What Should it be?
What Sprint 0 is NOT
• Assemble a team
• Teams happen & evolve
• Resources & logistics
• Space, desks, computers will evolve
• Project planning, backlog initialization,
design
• Kinda like waterfall
• Hinders scrum
What Sprint 0 Should Be
• Create basic skeleton and plumbing
• Future sprints add incremental value
• Minimal design upfront
• Evolving design emerges later
• Enough framework to permit refactoring
Source: 2013, What is Sprint Zero?, Anurag Prakash
https://www.scrumalliance.org/community/articles/2013/september/what-is-sprint-zero

4. Sprint 0: Is [should] there be any value delivered ???

5. Sprint 0: Not Sprint 1
Sprint 0 is the Starting Line
• Not the pre-project
• Not the preparation of a requirements document
• Not the project management framework
• Not culminating in a testable or deliverable item
• Has zero-duration
• May be a distinct introductory conclave (meeting)
• Is an identifiable event or occurrence
• Upholds organizational standards and construction
NoConsensusAmongPractitioners
Source: Mark Reynolds, compilation

6. Sprint 0: Why do we need a starting point?

7. Sprint 0: Life Before the Project
Life before the project
• Project is secured
• External: customer and project objectives
• Internal: organizational sponsor and project objectives
• Constraints and Environments are established
• Security
• Allowed / disallowed infrastructure
• Scoping the conclusion
• How the team may recognize the conclusion
• Not a “project before the project”
Source: Mark Reynolds, compilation

8. Sprint 0: From What Basis will Sprint 1 Initiate?
• The Team should be onboard
• Evolution and shifting will occur
• Sprint Framework should be defined
• Evolution and shifting will occur
• Definitions should be in place
• Who is the customer?
• What did the customer ask for?
• Who are the chickens and who are the pigs?
• Who are the project managers and overseers?
• What is the project template?
TheBalanceofthisPresentation
Source: Mark Reynolds, compilation

9. Sprint 0: What Project Aspects Included?
• Operational Infrastructure
• Application hosting
• Data hosting
• Security
• Development Infrastructure
• Components
• Architecture
• Testing
• Security

10. Sprint 0: Architectural Considerations
N-tier Perspectives
Source: Mark Reynolds, compilation

11. Sprint 0: Architectural Considerations
Source: Mark Reynolds, compilation
MVC (Model View Controller) vs MVVM (Model View ViewModel)

12. Sprint 0: Architectural Considerations
Source: 2011, Thinking DDD with Patterns
http://mouforum.blogspot.com/2011/05/thinking-ddd-with-patterns-part-1.html
Domain Driven Design

13. Sprint 0: Architectural Considerations
Source: 2013, Building End-to-End Multi-Client Service Oriented Applications, Miguel Castro
http://www.pluralsight.com/courses/building-multi-client-end-to-end-service-oriented-applications
Database Database
Client Tier
(Desktop Applications,
Unmanned Processes)
Presentation Tier (Web Browser)
UI (Client) Tier (IIS)
Business Tier (Service Proxies)
Service Layer
DAL / ORMDAL / ORM
Business Engine Business Engine
PluralSight: Building End-to-End Multi-Client SOA

14. Sprint 0: Demonstration
Project Demonstration Here.

15. Sprint 0: What is the ideal Sprint 0?

16. Mark Reynolds
Mark Reynolds Vitae
• Southwestern Energy
• Lone Star College
• Intent Driven Designs
• Scan Systems
• Sikorsky Aircraft
• General Dynamics
Personal Email: mark@DataDriven.Energy
Linkedin: www.linkedin.com/in/MarkDataDriven
Twitter: @MarkDataDriven
http://DigitalTransformation.Engineer
Copyright (c) 2015-2018 by Mark Reynolds 16