Project

Profile

Help

Going Agile with Planio » History » Sprint/Milestone 34

Thomas Carney, 06/29/2015 03:09 PM

1 21 Thomas Carney
# Agile
2 1 Thomas Carney
3 32 Thomas Carney
Planio lets you use agile methodologies such as Scrum, Kanban or Extreme programming for your projects.
4 1 Thomas Carney
5
{{>toc}}
6
7 3 Thomas Carney
## Agile Methodologies
8 2 Thomas Carney
9 1 Thomas Carney
Agile methodologies includes a group of software development methods such as Scrum, Kanban or Extreme programming. They’re all based on the idea that requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.
10
11 34 Thomas Carney
This tutorial will help you set up your account for one of these methodologies.
12 1 Thomas Carney
13
## What you can do with Planio's Agile App?
14
15 34 Thomas Carney
Once it’s set up, you'll be able to:
16 1 Thomas Carney
17 34 Thomas Carney
  - see all the sprint items on one board;
18
  - drag-n-drop items or update them on the board;
19
  - plan your sprints and create issue backlogs;
20
  - generate burndown charts, cumulative flow charts, velocity charts and more.
21 1 Thomas Carney
22 11 Thomas Carney
## Getting Set Up
23 1 Thomas Carney
24 34 Thomas Carney
Make sure that the Agile app is activated. Go to the **Apps** tab and install the Agile app.
25 14 Thomas Carney
26 1 Thomas Carney
![](01_install_Agile_app.png)
27
28 32 Thomas Carney
## Start Simple
29 15 Thomas Carney
30 34 Thomas Carney
We've found that you'll have the most success if you start off with a simple setup. Once you've completed a few sprints with Planio, you'll be in a better position to see which customizations make sense for you.
31 1 Thomas Carney
32 15 Thomas Carney
## Plan a Sprint
33 22 Thomas Carney
34 34 Thomas Carney
If you don't have any issues in your project, add some issues now. Then, once your project has issues, it's time to plan your next sprint. Click on **New Sprint**. Give a name to your new sprint such as Sprint #1 and set the **start date**. Now, you can drag an issue from the **Issues without sprint** column to the sprint you just created.
35 9 Thomas Carney
36 24 Thomas Carney
![](spring_planning_first_sprint.png)
37 16 Thomas Carney
38
## View Items on Your Agile Board and Create Sprint Views
39
40 26 Thomas Carney
Click on **Agile board** in the navigation bar and you'll see the the issues laid out on the Agile board. By default, you'll see all issues in the project, rather than just the issues for the current sprint.
41 1 Thomas Carney
42 34 Thomas Carney
Therefore, we'll create and save a filter for the current sprint. Click on **Add filter** in the top right hand corner and select the **Sprint/Milestone**. Make sure the **Sprint/Milestone** is set to the current sprint and click **Save**.
43 26 Thomas Carney
44
![](Set_sprint_filter.png)
45 16 Thomas Carney
46 27 Thomas Carney
On the next page, you can **name** this filter, make it **visible to all users** and set it as the **default board**, so you don't have to select this filter each time.
47
48
![](new_agile_board.png)
49 17 Thomas Carney
50 34 Thomas Carney
It will appear in the right sidebar under **My agile boards**.
51 20 Thomas Carney
52 28 Thomas Carney
You can now drag and drop issues on your Agile board. You can also update items by right-clicking on them (Windows) or double-clicking on them (Mac).
53
54 29 Thomas Carney
![](Update_issues_on_board.png)
55 28 Thomas Carney
56 1 Thomas Carney
## Graphs, Graphs, Graphs!
57 17 Thomas Carney
58 30 Thomas Carney
Click on **Add filter**, select **Sprint/Milestone** and set it to the current sprint, so you can see the charts as they relate to the current sprint.
59 1 Thomas Carney
60 33 Thomas Carney
**Burndown charts** show you how a project is progressing. They highlights the impact of adding new feature requests, and they'll let you know if things aren't going according to plan.
61 18 Thomas Carney
62 1 Thomas Carney
![](Issues_burndown_chart.png)
63 30 Thomas Carney
64 33 Thomas Carney
The **velocity chart** shows you the output of a team per sprint.
65 1 Thomas Carney
66
![](velocity_chart.png)
67 31 Thomas Carney
68 33 Thomas Carney
**Lead time** is the time between an issue being opened and being closed. Teams using a Kanban approach often favor this method over the velocity chart, and they'll focus on improving the lead time rather than velocity.
69 1 Thomas Carney
70 31 Thomas Carney
![](lead_time_charts.png)
71
72 33 Thomas Carney
**Cumulative flow** shows how issues are 'flowing' through different statuses.
73 31 Thomas Carney
74
![](cumulative_flow_chart.png)
75
76
This chart helps answer questions such as:
77 18 Thomas Carney
78
1.  Are issues reaching their final state?
79
2.  Is there a particular status that's tacking a lot of time?
80
3.  How long does it take you to go from an idea to value?
81
4.  Is the scope of the project changing over time?