Agile Project Management Tools

University of Southern California

Center for Systems and Software Engineering

Agile Project Management Tools

Supannika Koolmanojwong

CSCI 577a



Outline• Agile Iteration Planning• Retrospective Analysis• Risk Management

2



Agile Iteration Planning• Define categories of your project status for

the next iteration– To do, Doing, Done– Goals, Tasks, WIP, Done

3http://accurev.com/blog/2010/09/27/implementing-agile/



Alternative Agile Boards

4http://theagileschool.blogspot.com/



Big Picture

5http://www.planbox.com/blog/category/agile-project-management



Burndown Chart

6http://www.infoq.com/articles/agile-kanban-boards



Tricks

7http://www.xqa.com.ar/visualmanagement/



Workshop 1• For this iteration (now to DCR ARB)• Write

– 2 “To-do” tasks – 2 “Doing” tasks– 2 “Done” tasks

• Post on the board• Talk among team members• Add more, if needed

8

SK

Task Name

Hours Spent (for “Done”)Hours Estimated (for “to-do” and “Doing”)

9

Your initial



Retrospective Analysis• Think about the previous iteration (from

previous ARB to upcoming ARB)– Smiley Face: What I liked...

• Team coordination; progress of work– Sad Face: What I didn't like....

• Mr.X needs to step up; client has not given me Z– Light Bulb: What is now clear to me...

• Finally, we have a full time !!– Cloud: What is still cloudy.....

• When are we going to get the server ?




Agile Retrospective Board




Daily Retrospective Board

• Niko-niko Calendar (or Smiley Calendar)

• Puts a Smiley mark onto a calendar after the day's work, before leaving the team room.

• member's mental health and motivation viewpoint

11http://drdobbs.com/architecture-and-design/201807863



Workshop 2• Post them on the board

– Smiley Face: What I liked...• Team coordination; progress of work

– Sad Face: What I didn't like.... • Mr.X needs to step up; client has not given me Z

– Light Bulb: What is now clear to me...• Finally, we have a full time !!

– Cloud: What is still cloudy.....• When are we going to get the server ?

• Talk among team members• Add as necessary

12

SK



Managing RisksTraditional vs Agile (1)

Traditional Agile

Risk Management•Work with management and stakeholders •Formal Documentation

Risk Management•Work with the product owner, delivery team, and scrum master•No or informal documentation

Risk Identification•BPUF - big planning up front•Risk management meeting•PM creates this deliverable

Risk Identification•Daily identify risk on multiple levels:

• product vision• product roadmap• release planning• sprint planning• daily stand up

•Whole team is involved in Scrum ceremonies and transparency

13http://www.solutionsiq.com/resources/agileiq-blog/bid/71750/Managing-Risk-in-Scrum-Part-2




Traditional Agile

Risk Analysis•Review all of the risks identified during the identification meeting and perform quantitative and qualitative analysis•prioritize and score risks •Manager prepare risk report

Risk Analysis•Focus on qualitative risk analysis because of the sprint time boxes and constant feedback loops provided in scrum•Scrum masters help keep the team see the risks

Risk Response Planning• Develop options and actions •PM or part of the team create ways to avoid, mitigate, plan contingency, or accept the risks

Risk Response Planning•Happens real-time as risk is identified•whole team is involved in brainstorming ways to avoid, mitigate, contain or evade the risks





Traditional Agile

Risk Monitoring and Controlling•Status meetings to discuss new risks and updates to the risk

•PM facilitates the status meeting; usually weekly or monthly

Risk Monitoring and Controlling•transparency of the delivery team’s work via task boards, burndowns, daily standups, and end of sprint reviews provide information and forums for continuously monitoring risk

•whole team is involved in risk monitoring by providing data and feedback




Agile Risk Management Tools

16



Agile Risk Management Tools

17



Risk Radar Tool

18

Business Technical

http://www.bigvisible.com/tag/agile-project-management/

Coordination

Execution

Need all VPs

meeting

Challenge in training Sales Rep

Sync interface of

M1 – M5

Migrate data

from S2



Risk Radar Tool

19

Business Technical

http://www.bigvisible.com/tag/agile-project-management/

Coordination

Execution

Need all VPs

meeting

Challenge in training Sales Rep

Sync interface of

M1 – M5

Migrate data

from S2

Next Two Sprints

Next Four Sprints



Workshop 3• As a team, brainstorm the risk items • Use Risk Radar Tool

– Business /Technical – Coordination/Execution

20

Documents

Agile Project Management Tools