Time Line View and List View of Agile Projects

(Click on the video tutorial for more information on List View and Time Line for Agile)

Time Line view of Agile Projects

While the Kanban Board format is the more common view of an Agile project, PlanStreet Project Management product does support a Time Line View of your Agile project.

1. Start by viewing the Street Board of any agile project.
2. Click on ‘Time Line’ in the top toolbar.

The Time Line View of an Agile Project may be useful for project managers transitioning from Waterfall methodology to Agile as it allows you to see the project in a format that you are used to.

1. Note that User Stories that are still in the Backlog are not shown in the Time Line View because they have not been scheduled to be worked on yet. Also note that each user story has the same timeline as the Sprint it is in.
2. Hover the cursor over any of the Time Lines to see detailed information about the item.
3. You can change the view of the project to Days, Weeks, Months, Quarter and also Year depending on the project.

List View for Agile Projects

While the Kanban Board format is the more common view of an Agile project, PlanStreet Project Management product does support a List View of your Agile project.

1. Start by viewing the project’s Street Board.
2. Click on ‘List View’.

The List View of an Agile Project may be useful for project managers transitioning from Waterfall methodology to Agile as it allows you to see the project data in a format that you are used to. By scrolling to the right, you will also have a view of the actual hours logged against the project, and all the project’s financial information.

1. Note that User Stories that are still in the Backlog are not shown in the List View because they have not been scheduled to be worked on yet. Also note that each user story has the same timeline as the Sprint it is in. Sprints in Agile project turned into Phases when you click it on List View, and Stories changes into Tasks.
2. User Stories in Agile project methodology are planned to be completed in one Sprint so their duration is the same as the length of the Sprint.
3. Number of Work hours can be planned based on how resources are allocated to the User Stories but may not be of great value if the Sprints are 2-3 weeks in length.