Problem Detection and reolution (10%) Flashcards
how problems impact a project
diagnosing takes time that causes delays
changing allready dine work also does
small problem can lead to long delay this way
the cost of change
agile promotes frequent communication with the stakeholders in order to keep these costs low
the longer a bug will be unaddressed the more expensive it will be to fix it
- cause more work will have to be undone to fix it
- more stakeholders will be involved
technical debt
technical dent is a backlog of work not done in cleaning up the code in order to deliver faster
we need constant refactoring to reduce technical debt
create a safe and open environment
similar to agile leadership and agile teams agile focuses on creating a safe and open environment also helps in the problem solving domain.
allow people to communicate the problems before they pop up at a late stage
lead time
cycle time
lead time (to do to done) measures how long something takes to go through the entire process
cycle time (e.g. from doing to done) measures how long takes to go through part of the process
cycle time = WIP | Throughput
KNOW THIS FORMULA !!!
throughput = amount of work than can be processed in a system i.mn a given time
knowing the cycle time allows to make commitments to the customer when the work will be done
excessive wip is associated with a number of problems:
- hides bottlenecks
- carries the risk of potential rework
agile focuses on reducing cycle time
throughput: average amount of work a team can get done in a time period
(might also be due to a new person)
productivity: rate of efficiency that the work is done
defects
defects cycle time
defect rate
defects cost money
that is why defect cycle time is of importance
some teams measure it to keep costs low
defect rates
measures rate of defects that made it to the final product without being detected
variance analysis
when evaluating performance or results there will always be a certain amount of variance due to normal fluctuation. some variation is normal - do not be fooled by that.
causes of variation
accept common cause of variation and work against special causes of variations
check daily for example to detect special causes of variance
trend analysis
statistics that look into the future are more interesting than stats that report the past.
the interesting info is the trend not the actual number (of defects for example)
control limits
upper and lower limits help to determine the acceptable variation
how many points per month do we need to work ?
how many people should be in a scrum team?
wip is also a control limit
risk adjusted backlog
business value high
risk = anti value> priorities them lower
that is a risk adjusted backlog
this allows agile teams to focus on value production and risk avoidance
risk burndown graph
problem solving
as continuous improvement
engage the team
- consensus for the proposal
- broader knowledge base
- practical
- involved people work hard
- asking for help shows confidence