Please enable JavaScript.
Coggle requires JavaScript to display documents.
methodology risk assessment (benefits:question: (higher productivity,…
methodology
risk assessment
what :question:
deliver functionality 2-4 weeks
quality
faster
principles day to day interactions
deliver product
end with review
benefits:question:
higher productivity
better quality
reduce time to production
improve stakeholder satisfaction
improve team dynamics
happy team
developer decisions freedom
high quality, low risk
what makes it great:question:
information transparent
people adapt, inspect, based on current conditions
address pitfalls of
waterfall development
constantly changing requirements
underestimate time
resource cost
compromise software quality
inaccurate progress reporting
what delivered is what expected
frequent inspection
ensure progress
detect variances early
react with adjustments
scrum/stand-up meeting
team decide how problem resolved
backlog
time to deliver
rely on sprint
brief meeting not > 15 min
members prepared and present
scrum master focus on goal
agenda :!:
risk assessment
affected areas
user
architecture
testing
review
decision making
development effort
quality review
testing
business requirements and expectation
document analysis
affected areas
decision making
planning
sprint planning
assigning task
resource capacity
timing
risk mitigation
escalation
probability factor
explain business affect of risk
countermeasures to take
reduce chance of failure
carrying out/execute analysis
accountable
structure
easy tracking
manage effect
escalate
testing
risk & mitigation
reduce maintenance