The document discusses hiring an agile coach to help product owners understand scrum methodology and prioritize product backlogs. It provides checklists for setting up team rooms, establishing working agreements, configuring Rally for tracking backlogs and releases, and understanding the offshore team composition. The document also lists 10 things that should be done in Sprint 0 like identifying stakeholders, organizing the project, assessing risks and assumptions, defining vision and scope, gathering requirements, establishing the team, developing a schedule, documenting architecture, estimating budgets, and preparing development environments. A typical definition of done for Sprint 0 includes having a project charter, product backlog, team, architecture overview, schedule, and business case ready.

1. Hiring an agile coach at onshore to help POs:
 in getting an understandingof the scrummethodology
 getting them up to speed in terms of creatingand prioritizingtheproduct backlog
Checklist items 
 Team room
 Workingagreement
 Setting up Rally -
o access to the scrum team
o product backlogentered in Rally
o create releases in Rally
Understand from Gouthami about the offshore team composition
Sprint0 checklist:
RESOURCES -
● Are Team/PO/SM availablefor SprintZero?
● Are Team/PO/SM trained for Scrum?
● Are Stakeholders aware of their roles?
● Is Team trained for technologies used in the project?
● Is Team awareand ABLE to be cross-functional?
○ Developers = Testers
● Does Product Owner know how to write user stories?
○ As <> I want <> so that <>.
○ Priority
ENVIRONMENT -
● Are workstations/PCs ready? Necessary software
installed?
● Are servers ready? Necessary software installed?
● Are meeting facilities setup?
○ Conference?

2. ○ Team knows how use?
● Version control system?
● Is an onlineproject workspaceneeded?
● Is a physical whiteboard ready?
TECHNICAL -
● Is Team sureabout technical architecture?
● Coding conventions areclear to Team?
● Does Team know how to write unittests?
● Is automated build server setup?
○ Test coverage
○ Pass/Fail notifications
● Team knows how to deploy and Product
Owner knows how to do testing

3. 10 Things to do in Sprint 0
Quite often Scrum projects and teams assumethat they can startdeveloping as from day 1 of the project.
This is only partially trueand depends on your definition of ‘Start of the project’.
If ‘Start of the project’ for you is defined as “we have our team ready, give me the prioritized backlog,we’ll
estimate so we can startdeveloping”, then you can indeed startdeveloping immediately.
However in most of the cases,you don’t have a backlog,a team... ready when the GO for a project is given. In
these cases you need to do a ‘Sprint 0’.
DuringSprint 0, you need to do the set-up of your project and prepare the necessary deliverables to get started.
Typically you’ll havethese stories on your “Sprint0” sprintbacklog:
1. Who is or will be involved in the project?
Find out all stakeholders,projectboard member, Core Team members.
2. How will the project be organized?
Define your approach,communication plan,basic set-up …
3. What are the main risks & constraints, and assumptions
Clarify your risks,constraintand main assumptions (in timeboxed sessions).
4. What is the purpose and scope of the project (vision)
High level vision of expected outcome and implementation.
5. What do I want to develop?
Gather the business requirements and prepare the product backlog.
6. Who do I need to produce the product?
Get your team or teams together.
7. By When do we need to deliver something (first release, full project?)
Develop a high level schedulein planned burn-down chartand target velocity.
8. How are we going to build it?
(if applicable,mostly for larger projects) Document a high level architectureoverview with impacted applications
and their data-flow.
9. How much money do we need?
Estimate the required budget to get your project delivered.
10. Is the technical set-up ready or available?
Prepare your development, test, deployment, CI frameworks and environments.
A typical “Definition of Done” for a Sprint 0 could be:
 Project Charter ready (containingvision,stakeholders,approach,…)
 Product Backlogready ( prioritized and estimated requirements)

4.  Team ready (who is goingto work on the project)
 Architecture Overview done (applicationsand data/communication flow)
 High level schedule/ burn-down chartready
 High level business caseready