Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

EM Software Development > 7. Retrospectives > Flashcards

7. Retrospectives Flashcards

1
Q

what is software process improvement

A
  1. looking at the big picture
  2. identifying areas that can be improved
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

what is software process improvement

A

software engineering processes encompass whole range of practices intended to support quality assurance
1. planning
2. version control
3. continuous integration
4. automated testing
5. code reviews
6. continual refactoring

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

process improvement frameworks

A
  1. iso9001
  2. six sigma
  3. capability maturity model (CMML)
  4. agile process improvement
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

capability maturity model level CMML

A
  1. initial
    - software process is ad-hoc or even chaotic
  2. repeatable
    - basic project management processes are established to track cost, schedule, functionality
  3. defined
    - software process for management and engineering activities is documented, standardised, integrated into the standard process for team
  4. managed
    - detailed measures of software process and product quality collected
  5. optimising
    - continuous process improvement enabled by quantitative feedback
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

principles for agile process improvement

A
  1. measurement is domain-specific
  2. improvement is an ongoing process
  3. requires full team participation
  4. best effort assumption
    - working harder won’t improve the process
    - blaming is pointless and counterproductive
  5. fix root causes, not symptoms
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

process-improvement process

A
  1. gather data about the process
  2. analyse
  3. identify actions
  4. prioritise and implement
    repeat…
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

scrum retrospective elements

A
  1. timing
    - occurs at the end of the sprint, after sprint review meeting with the customer
  2. participants
    - whole development team. scrum master acts as facilitator
  3. duration
    - at least 30 mins to allow proper data gathering
  4. data source
    - team members and project artifacts
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

general method to gather data from team members

A
  1. team members populate template board independently using sticky notes
  2. similar items are grouped together
  3. team votes on priority issues for discussion
  4. select action for improvement
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

template

A

stop, start, continue/more of

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

how to identify opportunities for improvement in performance

A
  1. team members provide detailed information fo the performance of the team
  2. project artifacts provide alternative source of information about project’s historical performance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

process improvement standards and models

A
  1. characterisation standard used to relate metrics gathered to assess maturity of team’s quality assurance process
  2. management standards explain methods and activities to undertake to conduct SPI effort
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

elicitation techniques

A
  1. theme boards
    - liked, learned, lacked, long for
  2. 5 whys
    - diagnosing problem root causes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

choosing improvement actions based on

A
  1. priority
  2. feasibility
  3. return on investment
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

monitoring and measuring

A
  1. creates tickets for the next release
  2. ensure someone is responsible for each activity
  3. include previous decisions in future retrospective
  4. review the process review process
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

drawbacks of team retrospectives

A

retrospective meeting may only take place every 2-4 weeks
1. problem left to persist for 2 -4 weeks
2. problems noted during sprint may not be recalled in the retrospective
3. details and circumstances may be forgotten

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

what does continuous process improvement mean

A

adopt continuous approach to process improvement. diagnose, apply solution to problem as soon s they are identified.
1. problems can be quickly dealt with
2. may mean that team is not involve in diagnosis or implementation of solution
3. may be disruptive to overall software process

as a compromise, diagnose and recommend solution in real time. discuss with team during retrospective

17
Q

retrospective meetings can become stale

A

important to
1. vary structure
2. reflect on retrospective itself
3. experiment with different frequencies
4. allow other team members to facilitate

18
Q

What are Retrospectives?

A

In Agile development, a retrospective is a meeting held at the end of each iteration to discuss what was successful, what could be improved, and how to incorporate the improvements and retain the successes in future iterations. Retrospectives cover topics such as the process, people, organizations, relationships, and tools. Regularly conducted retrospective meetings, when appropriate follow up activities occur, are critical to self-organization and continual improvement of development and testing.

19
Q

Advantages of Retrospectives?

A

Retrospectives can result in test-related improvement decisions focused on test effectiveness, test productivity, test case quality, and team satisfaction. They may also address the testability of the applications, user stories, features, or system interfaces. Root cause analysis of defects can drive testing and development improvements. In general, teams should implement only a few improvements per iteration. This allows for continuous improvement at a sustained pace.

20
Q

Timings of Retrospectives?

A

The timing and organization of the retrospective depends on the particular Agile method followed. Business representatives and the team attend each retrospective as participants while the facilitator organizes and runs the meeting. In some cases, the teams may invite other participants to the meeting.

21
Q

Testers role in Retrospectives?

A

Testers should play an important role in the retrospectives. Testers are part of the team and bring their unique perspective [ISTQB_FL_SYL], Section 1.5. Testing occurs in each sprint and vitally contributes to success. All team members, testers and non-testers, can provide input on both testing and non-testing activities.

22
Q

Testers role in Retrospectives?

A

Testers should play an important role in the retrospectives. Testers are part of the team and bring their unique perspective [ISTQB_FL_SYL], Section 1.5. Testing occurs in each sprint and vitally contributes to success. All team members, testers and non-testers, can provide input on both testing and non-testing activities.

23
Q

Why is trust an important aspect of Retrospectives?

A

Retrospectives must occur within a professional environment characterized by mutual trust. The attributes of a successful retrospective are the same as those for any other review as is discussed in the Foundation Level syllabus [ISTQB_FL_SYL], Section 3.2.

EM Software Development (22 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions