Sprints Planning Guidelines

1. Purpose ............................................................................................... 1 2. Guidelines ........................................................................................... 1

PURPOSE
The purpose of this document is to communicate best practices to be attempted to support planning of Sprints in the context of the Product Development Methedology so as to ensure better predictability in our process. Please note it is not a procedure or a policy.

GUIDELINES
1. Sprints may be conceived to be of one of the these two: A. Design Sprint B. Execution Sprint 2. Design Sprint. A Sprint that is focused on eliminating all Solution and Technical Design ambiguity for a given set of Business Needs defined by Marketing. 3. Execution Sprint. A Sprint is focused on executing on all or a portion of backlog so that the scope is appropriately sized for execution within the duration of the sprint. 4. Sequence. For a given scope of Business Needs one Design Sprint may be followed by one or more Execution Sprints that execute on that scope. 5. Design Sprint Review. At the Sprint Review for a Design Sprint the following artifacts is expected: A. A well-groomed (complete) backlog of Stories for Epics or Features laid out by Product Marketing (in a Google Doc) B. Every Story is sized for Portal, Messenger and Back-end effort C. Stories prioritized by Product Marketing D. Architecture Document if required, approved by Architecture Committee E. Design Documents if required, published to team F. UI Interfaces if any, published to team G. API if any, interfaces published to team H. Sprint tasking completed 6. Execution Sprint Review. At the Sprint Review for an Execution Sprint the team will execute the stories committed for the Sprint. 7. Can i squeeze in Execution in a Design Sprint? A Sprint has to be either a Design Sprint or an Execution Sprint. Execution should not be done in a Design Sprint. If there is Execution, it needs to be done in a separate Sprint.

Capsilon Corporation

Company Confidential

Page 1 of 3

8. Team organization. Teams may be organized to be in a Design Sprint or an Execution Sprints. There may be multiple Design and Execution Sprints running in parallel with different teams on different scope. 9. Scheduling Vacations & Travel. Members of the design team that have been named in the design sprint will not have any travel or vacations planned 10. Design Sprint Kickoff. A clear set of goals with measured by criteria for the design sprint will be agreed to at launch. The design team will be clearly defined by name to include members from engineering and product marketing. 11. Execution Sprint Kickoff. Product Marketing will approve scope of execution in a Sprint based on sizing provided by the team. Since the scope of the Execution Sprint is expected to be very clear Sprint Kick-offs are expected to be short and precise where the sprint planning primarily involved tasking and execution. 12. Design Sprint Duration. Design Sprints will be time-bounded to a not-laterdate. Which means, if the team feels it has sufficient clarity earlier, an Sprint Review may be called to close the Sprint and launch an Execution Sprint. Typical time durations will be for a week and in exceptional cases 2 weeks. 13. Execution Sprint Duration. Execution Sprints will be typically for two weeks with exception cases of 3 weeks. 14. Daily Deliverables will be maintained for Design Sprints as design artifacts.

Capsilon Corporation

Company Confidential

Page 2 of 3

Revision History Date Changed By

Sep 15, 2010 Sep 16, 2010 Murali Murali

Change
Initial draft based on discussion with Sanjeev and Julian Modifications suggested by Jeff on Design Sprint Kickoff & Vacations & Travel

Sep 20, 2010

Murali

Daily Deliverables of

Capsilon Corporation

Company Confidential

Page 3 of 3