Project

Profile

Help

Going Agile with Planio » History » Sprint/Milestone 58

Jan Schulz-Hofen, 01/25/2017 01:17 PM

1 45 Thomas Carney
# Setting Up Your Planio Account for Agile Project Management
2
3 39 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 43 Jan Schulz-Hofen
[Agile methodologies](https://plan.io/agile-project-management/) 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 1 Thomas Carney
11 34 Thomas Carney
This tutorial will help you set up your account for one of these methodologies.
12 1 Thomas Carney
13 47 Thomas Carney
## What can you do with Planio's Agile App?
14 1 Thomas Carney
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 41 Thomas Carney
Make sure that the Agile app is installed. Go to the **Apps** tab and install the Agile app.
25 1 Thomas Carney
26 57 Jan Schulz-Hofen
{{figure(Make sure the App is installed)
27
!installed-app-borderless@2x.png!
28
}}
29 1 Thomas Carney
30 32 Thomas Carney
## Start Simple
31 15 Thomas Carney
32 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.
33 1 Thomas Carney
34 15 Thomas Carney
## Plan a Sprint
35 22 Thomas Carney
36 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.
37 9 Thomas Carney
38 58 Jan Schulz-Hofen
{{figure(Drag and drop issues onto the next sprint)
39
!sprint-planning@2x.png!
40
}}
41 16 Thomas Carney
42
## View Items on Your Agile Board and Create Sprint Views
43
44 54 Thomas Carney
Click on **Agile board** in the navigation bar and you'll see 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.
45 1 Thomas Carney
46 47 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**.
47 1 Thomas Carney
48 48 Thomas Carney
![](filter-sprint@2x.png)  
49 42 Thomas Carney
*Set the filter to show the current sprint*
50 1 Thomas Carney
51
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.
52 27 Thomas Carney
53 48 Thomas Carney
![](save-agile-board@2x.png)  
54 42 Thomas Carney
*Save this board as the default board*
55 34 Thomas Carney
56 1 Thomas Carney
It will appear in the right sidebar under **My agile boards**.
57
58 20 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).
59 28 Thomas Carney
60 48 Thomas Carney
![](agile-board-with-menu@2x.png)  
61 42 Thomas Carney
*Update issues directly from the Agile board*
62 1 Thomas Carney
63 49 Thomas Carney
## Story Points
64
65 56 Thomas Carney
Estimating stories in terms of hours can lead to unproductive discussions about the exact amount of time a story will take. Mike Cohn [gives the example](https://www.mountaingoatsoftware.com/blog/the-main-benefit-of-story-points) of two runners discussing how long a 5K run will take. For one it may be 25 minutes, whereas for someone else it may be 45 minutes. Everyone, however, can agree that a 5K run is much shorter than a marathon.
66 49 Thomas Carney
67 56 Thomas Carney
In a similar vein, story points let you move away from debating exactly how long a story will take and start talking about the relative investment for each story. In order to avoid points just being seen as hours, some teams use the Fibonacci sequence of 0, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, etc. Therefore, instead of arguing over whether a story is a 7 or an 8, you can quickly agree that it’s more of an 8 than a 5, but not a 13-pointer.
68 49 Thomas Carney
69 52 Thomas Carney
In Planio, you can switch on story points by going to **Administration** -\> **Agile Board** and selecting **Story Points** as the estimate units.
70 49 Thomas Carney
71
![](estimate-units@2x.png)  
72
*Select Story Points as the estimate units*
73
74 55 Thomas Carney
Then, select which **trackers** should use story points. For example, you could have a tracker called User Stories that is the only one that uses story points. Alternatively, you can use story points for all trackers.
75 49 Thomas Carney
76 53 Thomas Carney
Now, you’ll be able to assign story points to issues when you create them. You can display story points on cards on the Agile Board, and you can have story points as columns in the issue list. You'll also have story point burn-up and burn-down charts.
77 49 Thomas Carney
78
![](agile-board-with-story-points@2x.png)  
79
*Agile Board with Story Points*
80
81 17 Thomas Carney
## Graphs, Graphs, Graphs!
82 1 Thomas Carney
83
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.
84
85 54 Thomas Carney
**Burndown charts** show you how a project is progressing. They highlight the impact of adding new feature requests, and they'll let you know if things aren't going according to plan.
86 1 Thomas Carney
87 42 Thomas Carney
![](burndown_chart.png)  
88
*Burndown Chart*
89 33 Thomas Carney
90 1 Thomas Carney
The **velocity chart** shows you the output of a team per sprint.
91
92 42 Thomas Carney
![](velocity_chart.png)  
93
*Velocity Chart*
94 1 Thomas Carney
95
**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.
96 31 Thomas Carney
97 42 Thomas Carney
![](lead_time_chart.png)  
98
*Lead Time Chart*
99 36 Thomas Carney
100 31 Thomas Carney
**Cumulative flow** shows how issues are 'flowing' through different statuses.
101 33 Thomas Carney
102 42 Thomas Carney
![](cumulative_flow_chart.png)  
103
*Cumulative Flow Chart*
104 31 Thomas Carney
105 35 Thomas Carney
Cumulative flow charts help answer questions such as:
106 18 Thomas Carney
107
1.  Are issues reaching their final state?
108 46 Thomas Carney
2.  Is there a particular status that's taking a lot of time?
109 18 Thomas Carney
3.  How long does it take you to go from an idea to value?
110
4.  Is the scope of the project changing over time?