Please enable JavaScript.
Coggle requires JavaScript to display documents.
Project Management, Self organising team, Workshops, Agile practices,…
Project Management
Selecting framework through analysis of size and scope of project
Agile
Principles
Can be blended
Why
Waterfall
Essentials
Stakeholder management
Time
Planning
Admin structures
Cost
Resources
Strategic goals
Realistic plans for goals
Project deliverables
Aligned with organisational goals
Timeplan
Lifecycle
Manage conflict
Ethics
Research
Role of project manager
Self organising team
Collaboration
all in it together
ask questions
Emergent leaders
Team free to experiment and problem solve
Trust
Open and honest comms
Workshops
Story writing
Prune the product tree
Speed boat sail boat
Buy a feature
Agile practices
Scrum
transparency
visibility
Most common
Inspection
Adaptation
Short sprints
product owner
Scrum master
Development team
Activities
Sprint backlog
Product backlog
Product increment
Safe environment
Leadership
Value individuals
Demonstrate trust
Generous assessing mistakes
Focus on failing and learning from mistakes
Keep commitments
lead by example
Sharing of information
Level playing field
Stakeholders
Information radiators
Big visible charts
2 more items...
2 to 4 weeks
4 to 12 people
eXtreme practices (XP)
Pair programming
Test driven development
Outcome focused
Value driven delivery
Value = product
Value for customer
Vertical Slicing
Defining value
What does success look like
Acceptance criteria
Agile
Small bites
Minimal viable products
Dispense money
display balances
Minimal market feature
Early feedback
Deliver value
Show customer small successes
show how product works overall
Keeps stakeholder engagement
Scope creep
Welcome changing requirements
Prioritise backlog
What customer values most is highest value backlog
Kano
meet with stakeholder to prioritise backlog
Exciters
Important
Satisfier
Thing that should obvs be there
Dissatisfier
Customer dislikes if not there
Indifferent
Customer doesn't care about Colour of ATM
Troublesome if lots of stakeholders
MoSCoW
Must have
Should have
Could have
Would like to have but not now
Research other prioritisation techniques
Stakeholder Engagement
Identify
Brainstorm who affect by product
Direct users
Product output
Secondary roles who care what you're doing
Educate about agile
Common fears
Sponsors - Success rates - stats
Managers - self managing team
Developers - autonomy
Users - closely engaged
Frequent but small chunks
Specific about time needed
Convergence
Participartory decision making
All voices heard
One person one vote
Thumbs up down sideways
Unless everyone thumbs up discussion must take place
Fist of five
number of fingers people vote with
Vote 0,1 or 2 need to disclose reason or concern
Once everyone votes 3,4,5 then can move on
agile charter
Goal of project
Need to have discussion
W5H
who is engaged
What will project be about
Where will work happen
When start and end date
Why is project needed
How will you work
Does not replace visioning session or definition of done
Agile modelling
Wireframe
flowchart
Personna
who is the customer
how they'll interact with the product
Managing stakeholders
Work with them
team
Autonomy
Empirical process
Flexible thnking
Agile Mindset
Live
Lead
Demonstrate
Status reports
Active feedback
Best face to face
2 way communication
Transparancy
Charter
Vision
Sprints
Release plan
Burn charts
Project risks
Quality defect status
Road map
Adaptive planning
plan to change your plan
plan releases
Smaller pieces
Plan today to meet iteration directive
Rolling wave planning
Revisit and adapt plans throughout life of project
Progressive elaboration - new info, reprioritise backlog
Agile at work series
Value driven delivery
Planning best practice
Risk management
Continuous improvement