7. Retrospectives Flashcards
1
Q
what is software process improvement
A
- looking at the big picture
2. identifying areas that can be improved
2
Q
what is software process improvement
A
software engineering processes encompass whole range of practices intended to support quality assurance
- planning
- version control
- continuous integration
- automated testing
- code reviews
- continual refactoring
3
Q
process improvement frameworks
A
- iso9001
- six sigma
- capability maturity model (CMML)
- agile process improvement
4
Q
capability maturity model level CMML
A
- initial
- software process is ad-hoc or even chaotic - repeatable
- basic project management processes are established to track cost, schedule, functionality - defined
- software process for management and engineering activities is documented, standardised, integrated into the standard process for team - managed
- detailed measures of software process and product quality collected - optimising
- continuous process improvement enabled by quantitative feedback
5
Q
principles for agile process improvement
A
- measurement is domain-specific
- improvement is an ongoing process
- requires full team participation
- best effort assumption
- working harder won’t improve the process
- blaming is pointless and counterproductive - fix root causes, not symptoms
6
Q
process-improvement process
A
- gather data about the process
- analyse
- identify actions
- prioritise and implement
repeat. ..
7
Q
scrum retrospective elements
A
- timing
- occurs at the end of the sprint, after sprint review meeting with the customer - participants
- whole development team. scrum master acts as facilitator - duration
- at least 30 mins to allow proper data gathering - data source
- team members and project artifacts
8
Q
general method to gather data from team members
A
- team members populate template board independently using sticky notes
- similar items are grouped together
- team votes on priority issues for discussion
- select action for improvement
9
Q
template
A
stop, start, continue/more of
10
Q
how to identify opportunities for improvement in performance
A
- team members provide detailed information fo the performance of the team
- project artifacts provide alternative source of information about project’s historical performance
11
Q
process improvement standards and models
A
- characterisation standard used to relate metrics gathered to assess maturity of team’s quality assurance process
- management standards explain methods and activities to undertake to conduct SPI effort
12
Q
elicitation techniques
A
- theme boards
- liked, learned, lacked, long for - 5 whys
- diagnosing problem root causes
13
Q
choosing improvement actions based on
A
- priority
- feasibility
- return on investment
14
Q
monitoring and measuring
A
- creates tickets for the next release
- ensure someone is responsible for each activity
- include previous decisions in future retrospective
- review the process review process
15
Q
drawbacks of team retrospectives
A
retrospective meeting may only take place every 2-4 weeks
- problem left to persist for 2 -4 weeks
- problems noted during sprint may not be recalled in the retrospective
- details and circumstances may be forgotten
