Pankaj is a very intelligent guy and has been involved in Agile for last 3-4 years. Under Pankaj's leadership his company has grown from 2 developers to 140 developers in just 2 years time. In the conference call with John, Pankaj introduces himself and Deepak, to Sean and John, and then explains the process his company follows for each project they get to develop. He explains how they use an Agile Software Development Tool to keep track of the requirements, tasks, defects etc and to measure team velocity and project burn-down. Deepak is a trained ScrumMaster and will be leading this project. Sean and Deepak discuss technology, architecture, schema and other product details. Once Deepak becomes clear of the business scope he asks John to send him code base repository access, use cases (requirements) and any other documents prepared by the onsite team. The call is signed off after arranging another call for next week, at 08:00 am CST where Deepak will discuss first iteration plan outlining stories and estimates. Also, John and Sean express a wish to meet the complete development team during this call.
The next day, Deepak receives emails from John regarding the product. He studies product requirements, checks source code, prepares his development machine, creates new project on an Agile tool - Scrumy - and creates enough stories for the product backlog. On the second day Deepak builds his team, explains the product to the team and organises a meeting to discuss stories and estimates. The team has 3 developers and 1 QA. During meeting the next day, the team estimates each story and Deepak updates stories on Scrumy with the estimates. In the evening Deepak sends out an email to John and Sean (cc: Pankaj) with their login details to Scrumy asking them to provide their feedback and to prioritize the stories.
Once stories are accepted and prioritized by John, Deepak will pick stories with high priority and will create iteration1 lasting for 2 weeks. All the stories are estimated relative to the story that would take the least time to get developed. Each story estimate considers unit testing and acceptance testing time taken.
The next week, during the conference call Deepak introduces team to John and Sean. All team members introduce themselves with a) background b) experience and qualifications c) Agile experience. Sean discusses both technical details and business scope of the product with the team to make them comfortable. John asks Deepak for weekly demonstrations to feel comfortable and remain updated about what's going on, every week, at other side of the world. Deepak agrees to weekly demonstrations considering it as a good opportunity to gain John's trust and signs off the conference call after arranging a weekly call every Friday at 08:00 am CST for next 3 months. Deepak creates a wiki account for this project on company's wiki server, and posts all documents, conference calls transcripts on it. An email is sent out to both onshore and offshore teams with everyone's Skype accounts and cell phone details.
The first iteration starts on Monday with a daily morning standup meeting where Deepak asks each team member to mention stories he/she will be working on today. The meeting goes on for 15-20 minutes, and after the meeting each team member logs on to Scrumy and updates it after picking stories. At the end of each day the team commits source code changes to code base repository. Deepak then reviews the code, prepares new builds after verifying all unit and acceptance tests pass and updates wiki with standup meeting report.