Going Agile with Planio » History » Sprint/Milestone 22
Thomas Carney, 06/26/2015 04:18 PM
1 | 21 | Thomas Carney | # Agile |
---|---|---|---|
2 | 1 | Thomas Carney | |
3 | 21 | Thomas Carney | Planio lets you use agile methodologies such as Scrum, Kanban or Extreme programming. |
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 | We’ll look at how you can use Planio for one of these methodologies. |
||
12 | |||
13 | ## What you can do with Planio's Agile App? |
||
14 | |||
15 | Here’s what it will look like once it’s set up: |
||
16 | |||
17 | - 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 | |||
22 | 11 | Thomas Carney | ## Getting Set Up |
23 | 1 | Thomas Carney | |
24 | First, create a new project in Planio. |
||
25 | |||
26 | 14 | Thomas Carney | Then, make sure that the Agile app is activated. Go to the Apps tab and install the Agile app. |
27 | |||
28 | 1 | Thomas Carney | ![](01_install_Agile_app.png) |
29 | |||
30 | 15 | Thomas Carney | ## Keep It Simple & Snappy |
31 | |||
32 | We've found that you'll have the most success if you start off with a simple set-up and work from there. Once you've completed a few sprints with Planio, you'll be in a better position to see what customizations will make sense for you. |
||
33 | |||
34 | ## Create the Backlog column |
||
35 | |||
36 | 14 | Thomas Carney | Click on the 'Agile board' in the navigation bar. Then, click on 'Sprint planning' under Issues in the right sidebar. Click on 'New Sprint'. |
37 | 1 | Thomas Carney | |
38 | 22 | Thomas Carney | ![](create_a\_new_sprint.png) |
39 | |||
40 | 1 | Thomas Carney | Name this sprint 'Backlog' and don't give it any date. |
41 | |||
42 | 21 | Thomas Carney | ![](create_a\_new_sprint.png) |
43 | |||
44 | 14 | Thomas Carney | Then, we'll move stories into the Backlog column. You can use the Issues without sprint column as an Icebox. |
45 | 22 | Thomas Carney | |
46 | ![](sprint_planning_backlog.png) |
||
47 | 1 | Thomas Carney | |
48 | 14 | Thomas Carney | ## Plan a Sprint |
49 | 7 | Thomas Carney | |
50 | 8 | Thomas Carney | You now have a backlog of items, and it's time to plan your next sprint. Click on the 'Agile board' tab in the navigation bar. Then, click on 'Sprint planning' under Issues in the right sidebar. Click on 'New Sprint'. |
51 | 7 | Thomas Carney | |
52 | 15 | Thomas Carney | Give a name to your new sprint such as Week 27 2015 and set the start date. |
53 | 9 | Thomas Carney | |
54 | Now, you can drag an issue from the Backlog column onto the sprint you just created. |
||
55 | 16 | Thomas Carney | |
56 | ## View Items on Your Agile Board and Create Sprint Views |
||
57 | |||
58 | 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. |
||
59 | |||
60 | 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 filter is Sprint / Milestone is set to the current sprint and click 'Save'. |
||
61 | |||
62 | On the next page, you can name this filter and set it as the default board, so you don't have to select this filter each time. |
||
63 | 17 | Thomas Carney | |
64 | 20 | Thomas Carney | It will appear in the right sidebar under 'My agile boards'. |
65 | |||
66 | 17 | Thomas Carney | ## Graphs, Graphs, Graphs! |
67 | |||
68 | Burn down 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. |
||
69 | 18 | Thomas Carney | |
70 | 19 | Thomas Carney | The velocity chart shows you the output of a team per sprint. |
71 | 18 | Thomas Carney | |
72 | 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. |
||
73 | |||
74 | Cumulative flow shows how issues are 'flowing' through different statuses. This chart helps answer questions such as: |
||
75 | |||
76 | 1. Are issues reaching their final state? |
||
77 | 2. Is there a particular status that's tacking a lot of time? |
||
78 | 3. How long does it take you to go from an idea to value? |
||
79 | 4. Is the scope of the project changing over time? |