Identify the Stakeholder Level:
#BusinessAnalysis #BusinessAnalyst #ProjectManagement #Agile #BAMindset #Efficiency #DataStrategy defining a few of these 123 tools? Scrum Framework: Roles (PO, SM, Team), Events (Sprint,
- Scrum Framework: Roles (PO, SM, Team), Events (Sprint, Daily Scrum, Review, Retro), Artifacts (Backlog, Increment).
- Kanban: Visualizing workflow with a board, limiting Work In Progress (WIP), and managing flow.
- Backlog Refinement (Grooming): Regularly cleaning, estimating, and prioritizing the product backlog.
- Planning Poker: Consensus-based estimation using Fibonacci / T-shirt sizes.
- Affinity Estimation: Grouping large numbers of user stories into like-sized buckets.
- Velocity Tracking: Measuring how many story points a team completes per sprint.
- Burndown / Burnup Charts: Tracking remaining work vs. time remaining.
- Spike: A time-boxed research activity to reduce uncertainty on a technical or functional issue.
- Continuous Integration / Continuous Deployment (CI/CD) Pipeline Analysis: Reviewing automated build and deploy steps.
- ADKAR Model: Individual change management (Awareness, Desire, Knowledge, Ability, Reinforcement).
- Kotter’s 8-Step Change Model: A top-down organizational change framework (Create urgency → Build coalition → Form vision → Communicate → Empower → Generate wins → Consolidate → Anchor).
- Change Impact Assessment: Mapping exactly which roles, processes, and systems will be affected by a change.
- Force Field Analysis (Lewin): Listing driving forces vs. restraining forces for a change; strategizing to strengthen drivers or weaken restrainers.
These techniques help you visualize complex processes and uncover root causes. Scrum Framework: Roles (PO
He wrote four letters vertically:
Must have
Should have
Could have
Won't have limiting Work In Progress (WIP)
Section 8: Change Management Techniques (10)