---
# System prepended metadata

title: Development plan
tags: [Build-Measure-Learn]

---

# Development plan

###### tags: `Build-Measure-Learn`

## What we have

### The Method

#### Sprints
- 2 week sprints;
- at least 2 weekly meetings;

#### Sprint Planning
**WHO?** - Team
**HOW?**- Video-conference
**WHEN?** - Friday morning, Start of the Sprint (11:00)

*Task list*
- View what is the Sprint Goal
- Choose User Stories related to that Sprint Goal (Sprint Backlog)
- List/Review tasks for each User Story
- Task Division

#### Daily Scrum
**WHO?** - Team
**HOW?**- Slack
**WHEN?** - Every Tuesday, 10:00

Each Tuesday a Slack bot would used on Slack so everyone can briefly talk a bit about his/her progress on the current Sprint tasks. The following questions should be answered in a thread:

*Task list*
- What have I done until now that is considered progress towards the Sprint Goal?
- What will I do this week?
- Is there anything that has become a barrier for my progress? If there is, explain


#### Sprint Review and Next Sprint Goal
**WHO?** - PO + Team
**HOW?** - Video-conference
**WHEN?** - Wednesday/Thursday afternoon

*Task list*
- List what was developed;
- Discuss what went well, what problems we had, and if they were solved;
- PO makes questions regarding the current Increment;
- Product Backlog revision;
- Review Resources we have related to the amount of work that is expected (team elements, time, effort, etc)
- What is going to be developed next sprint?
- What should the Sprint Goal be?

#### Sprint Retrospective
**WHO?** - Team
**HOW?** - Video-conference
**WHEN?** - Friday morning, End of the Sprint (10:30)

Before we start talking about the Sprint Planning on Friday meeting, we will do the Sprint Retrospective. The purpose of this is to understand what can be improved with regards to the team dynamics, and to keep a positive and productive meeting. Each one should participate (If you are going to repeat something, just say that you agree with what was already said), and talk about each of the following points:

*Task list*
- How did the last Sprint go with regards to people, relationships, process, and tools?
- Identify and order the major items that went well and potential improvements;
- Create a plan for implementing improvements to the way the Scrum Team does its work.


_____________________________________________________
_____________________________________________________

## Research

### Sprint Planning

    What needs to be answered?
    1. What can be done this Sprint?
    2. How will the chosen work get done?

**(1)** 
- DevTeam forecasts the functionality that will be developed;
- PO discusses what the Sprint Goal should be, and selects the Product Backlog items that lean towards that goal;
- DevTeam selects the number of items it will do, according to their capacity and past performance;
- The whole Scrum Team crafts the Sprint Goal, the objective to be met within the Sprint.

**(2)**
- DevTeam decides how to turn the functionality into a "Done" product increment;
- The Product Backlog items selected for this Sprint plus the plan for delivering them is called the Sprint Backlog;
- If the Development Team determines it has too much or too little work, it may renegotiate the selected Product Backlog items;
-  the Development Team should be able to explain how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment. 


### Daily Scrum

The Daily Scrum is a 15-minute time-boxed event for the Development Team. 

The structure of the meeting is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based. Here is an example of what might be used:
- What did I do yesterday that helped the Development Team meet the Sprint Goal?
- What will I do today to help the Development Team meet the Sprint Goal?
- Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

### Sprint Review

- A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed;

The Sprint Review includes the following elements:
- Attendees include the Scrum Team and key stakeholders invited by the Product Owner;
- The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”;
- The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;
- The Development Team demonstrates the work that it has “Done” and answers questions about the Increment;
- The Product Owner discusses the Product Backlog as it stands. He or she projects likely target and delivery dates based on progress to date (if needed);
- The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning;
- Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and,
- Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.

The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint.

### Sprint Retrospective

- The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
- The Scrum Master ensures that the meeting is positive and productive.
- The Scrum Master teaches all to keep it within the time-box.

The purpose of the Sprint Retrospective is to:
- Inspect how the last Sprint went with regards to people, relationships, process, and tools;
- Identify and order the major items that went well and potential improvements;
- Create a plan for implementing improvements to the way the Scrum Team does its work.


