Agile Concepts to know for the PMP Exam
- Agile contracts
- Agile Estimation Techniques
- Agile Planning
- Burndown / Burnup charts
- Product backlog (pg 131) -> scope baseline
- Cummulative Flow Diagram (in Kanban)
- Definition of Done
- Dreyfus model of Skill Acquisition
- Dot-Voting
- Epics
- Cadence and Timeboxing
- Kanban
- Iterative scheduling with a backlog
- On-demand planning (Kanban)
- Retrospectives
- Generalized specialist (an individual with deep knowledge in a particular specialization who has also learned to be productive in other team roles)
- Information Radiators
- Minimum Viable Product (MVP) vs MMF
- Personas
- Agile teams
- (T / I shaped)
- Self-organizing teams
- Servant Leadership
- Velocity
- Lean
- Scrum
- Shu-Ha-Ri
- Speed B. Leas
- Osmotic Communication
- User Story (pg 131) -> requirements
- Agile Triange of Constraints
- Myers-Briggs TT
- Doing Agile vs Being Agile
- Last Responsible Moment
- eXtreme Programming (XP)
- Value Stream Mapping (Lean)
Flow-based agile teams use different measurements: lead time (the total time it takes to deliver an item, measured from the time it is added to the board to the moment it is completed), cycle time (the time required to process an item), and response time (the time that an item waits until work starts). Teams measure cycle time to see bottlenecks and delays, not necessarily inside the team.
Techniques to make Virtual Teams more effective
- Online Collaboration tools such MS Office, Google Apps, MS Teams and Slack.
- Audio/Video conferencing such as Webex, MS Teams, Zoom, and Google Meet.
- Virtual workspace like “fishbowl window” which is a persistent video link between distributed teams. It helps to improve osmotic communication.
- Remote pairing (like pair programming) where two people work together on a single task. Tools such as audio/video conferencing and virtual whiteboard can help pairing more effective. Ideally the two people should be in the same or near time zone to have maximum overlap in their working hours.