PMI-ACP Study Notes: PART II

The six principles of Kanban

• Visualize the workflow
• Limit work in progress [WIP]
• Manage flow
• Make policies explicit
• Implement feedback loops
• Improve collaboratively, evolve experimentally

The seven principles of Lean

• Eliminate waste: maximize value
• Amplify learning: via frequent communication and feedback
• Decide as late as possible: Early planning, Late decision making.
• Deliver as Fast as possible: Maximize ROI
• Empower Team: self-managed and trusted.
• Build Quality In: Quality Assurance rather than Quality Control
• See the whole: See the system, not the parts of a system

The seven wastes of Lean Software Development

• Partially done work
• extra features
• relearning: Lack of documentation, poor coding practices, and consistent task switching between team members all create chaos as each one attempts to relearn something they moved on from in the past
• handoffs
• delays
• task switching
• defects

Definition of Done

Your team needs to know what done looks like, not just for the finished product or result, but at the end of each iteration.

User stories

User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system

The goal of any user story is to make sure that you can break it down to a specific, individual amount of work (about 1 to 3 days of work) and test it for completion.

Independent

Negotiable

Valuable

Estimable

Small

Testable