University of Southern California Center for Systems and Software Engineering Agile Project Management Tools Supannika Koolmanojwong CSCI 577a

University of Southern California Center for Systems and Software Engineering Outline Agile Iteration Planning Retrospective Analysis Risk Management 2

University of Southern California Center for Systems and Software Engineering Agile Iteration Planning Define categories of your project status for the next iteration –To do, Doing, Done –Goals, Tasks, WIP, Done 3

University of Southern California Center for Systems and Software Engineering Alternative Agile Boards 4

University of Southern California Center for Systems and Software Engineering Big Picture 5

University of Southern California Center for Systems and Software Engineering Burndown Chart 6

University of Southern California Center for Systems and Software Engineering Tricks 7

University of Southern California Center for Systems and Software Engineering 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

University of Southern California Center for Systems and Software Engineering 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 ? 9

University of Southern California Center for Systems and Software Engineering Agile Retrospective Board 10

University of Southern California Center for Systems and Software Engineering 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 11

University of Southern California Center for Systems and Software Engineering 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

University of Southern California Center for Systems and Software Engineering Managing Risks Traditional vs Agile (1) TraditionalAgile 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 13

University of Southern California Center for Systems and Software Engineering Managing Risks Traditional vs Agile (2) TraditionalAgile 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 14

University of Southern California Center for Systems and Software Engineering Managing Risks Traditional vs Agile (3) TraditionalAgile 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 15

University of Southern California Center for Systems and Software Engineering Agile Risk Management Tools 16

University of Southern California Center for Systems and Software Engineering Agile Risk Management Tools 17

University of Southern California Center for Systems and Software Engineering Risk Radar Tool 18 BusinessTechnical Coordination Execution Need all VPs meeting Challenge in training Sales Rep Sync interface of M1 – M5 Migrate data from S2

University of Southern California Center for Systems and Software Engineering Risk Radar Tool 19 BusinessTechnical 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

University of Southern California Center for Systems and Software Engineering Workshop 3 As a team, brainstorm the risk items Use Risk Radar Tool –Business /Technical –Coordination/Execution 20