Project Management Flashcards
What is Kanban?
- Visual cards
- Kanban board displays each user story on a card and move through columns
- Continuous development and delivery tracking a small number tasks fluidly and concurrently
- Work in progress (WIP) limits set helps remove blockers and bottlenecks
- If you have a continuous stream of work requests, kanban works well
What is a methodology?
A model which project managers employ for the design, planning, implementation and achievement of their project objectives.
Describe the risk management process.
• Risk identification
○ A checklist of common risks may be used to identify risks in a project
§ Technology risks -> database can it process enough transactions per second? Software components, can some cause problems?
§ People risks -> Is it possible to recruit staff with the skills required? Is further training required?
§ Organisational risks -> organisational financial problems. Organisation is restructured so that different management are responsible for the project.
§ Tools risk -> code generated by software code generation tools inefficient?
§ Requirements risks -> changes to requirements that require major design rework are proposed.
§ Estimation risks -> Time required to develop the software is underestimated. The rate of defect repair is underestimated. The size of the software is underestimated.
• Risk analysis
○ Assess probability and seriousness of each risk
§ Assign each a probability class .. Very low, low, moderate, high or very high
§ Assign each a effect class .. Catastrophic, serious, tolerable or insignificant
○ E.g. Organisational financial problems, the need to recruit staff with proper skill set, database faults
• Risk planning
○ Consider each risk and develop a strategy to manage that risk
○ Avoidance strategies
§ Coming up with strategies to lower the probability of a risk occurring
○ Minimisation strategies
§ Coming up with strategies to lower the impact of a risk if it did occur
○ Contingency Plans
§ Coming up with strategies to handle risks when they do occur
• Risk monitoring
○ Assessing each identifies risk regularly to determine whether or not it is becoming less or more probable
○ Risk monitoring tracks projects
§ Assess whether a predicted risk occurs
§ Assess whether the effects of the risk have changed
§ Ensures that risk aversion steps are defines and properly applied
Collects information that can be used in the future
Describe the four stages of the Tuckman development model.
- Forming
○ High dependence on leader for guidance and direction
○ Individual roles and responsibilities are unclear- Storming
○ Decision don’t come easily within group
○ Team members “fight” for position as they attempt to establish themselves in relation to other team members and the leader
○ Clarity of purpose increases but plenty of uncertainties persist - Norming
○ Agreement and consensus largely forms among the team, who respond well to facilitation by leader
○ Roles and responsibilities are clear and accepted - Performing
○ Team more strategically aware, team know why and what it is doing.
○ Team has shared vision and is able to stand on it’s own two feet with no interference or participation from the leader
○ Disagreements occur but now they are resolved within the team positively
- Storming
What is the main difference between Kanban and Scrum?
- Kanban there is a WIP limit
○ But the WIP tasks are flexible and can be swapped between the To-do column
Kanban tasks are organised by work priority
Describe Scrum technique.
- Regular fixed length sprints
- End of each sprint if approved by PO
- PO, Scrum master, dev team
- Velocity = # story points completed in sprint
Ideally no changes during sprint
What is lean?
- Process of eliminating waste from within a project, process or company
- Minimise waste and maximise value to the customer
- Empowering frontline workers, responding immediately to customer requests
○ Inventory - Partially work done
○ Extra processing - Paperwork or excess documentation
○ Overproduction - Extra features and processes
○ Transportation - Building the wrong thing
○ Waiting - Waiting for the information
○ Motion - Task switching
