Brainscape's Knowledge GenomeTM

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


See full index

Programming > Agile Software Developent: Release and Iteration Planning > Flashcards

Agile Software Developent: Release and Iteration Planning Flashcards

1
Q

3 main benefits of Release and iteration planning

A

Identify potential impediments

Communicate with stakeholders and customers

Provides Traceability

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

Questions to consider at the start of Release and Iteration planning

A

During release planning, the team focuses on groups of user stories or themes like security, reporting, login, dashboards, data clean up, UI enhancements that deliver a working and usable product.

What is the minimum set of features needed to be successful?

What themes should we focus on in this release?

Do the user stories align to deliver a fully functional feature?

Will the pieces result in something not fully functional yet? - If so, is this intentional, because there is a bigger picture, and this is a part of the process?

Does this plan equate to value?

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

Why does the team need a release plan?

A

To help the team focus on what is being delivered for the release

So stakeholders and customers can know what features to expect

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

How is velocity calculated?

A

measured numerically by calculating the average number of Story Points completed each sprint.

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

Which metric will a newly formed team not have access to when they plan a release?

A

Velocity

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

Release

A

The process of giving the latest version of the product to the customer or end-user

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

Agile process for getting to the Release

A
  1. Identify
    - Features identified or requested
  2. Plan
    - User stories are written and prioritized
  3. Build
    - Team implements the user stories
  4. Test
    - Verify it works
  5. Deploy
    - Release the software to customers
  6. Maintain
    Ensure that it continues to work
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Release Plan

A

Teams plan for completing user stories and functionality that will be included in a release

Made up of several iterations

shows which iteration user stories will be complete

Aligns user story implementation in a logical order

Is created in a release planning meeting

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

An iteration

A

A timed cadence used to plan, commit, and deliver work

Each iteration results in working software

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

What are iterations called in Scrum?

A

Sprints

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

How long is the typical sprint?

A

1 - 4 weeks

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

Should an iteration interval be changed once it has been set?

A

NO

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

Iteration Plan

A

Detailed and logical plan for implementing user stories

Shows teams commitment for completing user stories within an iteration

Only the user stories that the team can complete are included

Depends upon team’s velocity

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

Who creates the Release and Iteration Plans?

A

The PO prioritizes user stories based on value.

The team then estimates the user stories in the product backlog and determines how much of the prioritized work they can complete

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

What inputs are needed to create a Release and iteration Plan?

A

A prioritized backlog

Estimated user stories

Team’s velocity

Team’s availability

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

Burning down the release

A

Tracking the rate at which we are burning down the work

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

What does a burn-down chart show us

A

Measure how much work is remaining

Helps to determine team velocity

Lets us know if we are on track

Helps us understand the impact of adding user stories to the release

Displayed on Graph:

  • Y-Axis represents Story Points
  • X-axis represents weeks
18
Q

Before shipping software, we need to …

A

Verify acceptance criteria has been met

Validate that it is working as intended

Demo to customer

19
Q

How to manage bugs/defects discovered by the team?

A

Assess their value and impact. The software can still be released with defects if it provides value

Add to backlog

Be transparent about defects, by informing the customer and showing how and when you plan to fix it

20
Q

Escaped defects

A

defects that are not caught by the team, but by the customer after the software has been released

21
Q

A development team is building a product that has an upcoming release date. The team realizes they will not be able to complete all of the work that they committed to for the release. What should the team do?

A

Work with the Product Owner to prioritize and reduce the scope of the remaining work.

22
Q

MVP

A

The MInimal set of features the team needs to deliver for the product and customer to be successful

23
Q

Velocity

A

The amount of scope or user story points the team is able to complete each iteration

24
Q

How is velocity established for new teams

A

New teams need to complete 3 - 5 sprints to establish velocity

New teams estimate velocity for their first 3 - 5 sprints

25
Q

Velocity Equation

A

Total # of Story Points / # of Sprints

26
Q

Timebox

A

A set period of time to complete work. It should result in working software or proof that a concept will or won’t work

27
Q

Spikes

A

Risk management technique

A timeboxed deep dive that a development team uses to discover or prove if an approach will work

Used to determine technical and functional approaches

28
Q

CI - Continuous Integration

A

A software development practice in which developers merge code frequently into a shared code repository. This helps to discover and fix problems with code faster

29
Q

CD - Continuous Delivery

A

Perform frequent demo workin gsoftware to customers

Frequently release the workin gsoftware to customers

Give value earlier and more often

30
Q

A team is trying to determine the best architectural approach for the product they are about to build. What technique or tool should the team use to figure what approach will work best?

A

A Spike

31
Q

Sprint Planning

A

8 hours

  1. PO presents Prioritized Backlog
  2. Team reviews the priorities to gain clarity
  3. Team creates Sprint backlog by committing to deliver work they can complete
32
Q

Scrum 4 events

A
  1. Sprint Planning
  2. Daily Stand-up
  3. Retrospective
  4. Sprint Review
33
Q

Daily Stand-up

A

15 min a day

3 Questions

What did you do?
What do you plan to do?
What impediments are you facing?

34
Q

Sprint Reviews

A

1 hour
At the end of each sprint

Team members demo working software to customers and customers give feedback

35
Q

Retrospect

A

1 - 2 hours
At the end of each sprint

The team looks for ways to improve working processes

3 questions

What went well?
What didn’t go well?
What actions should we take to improve?

36
Q

What happens with work not done during a sprint?

A

It gets placed back into the product backlog where it gets prioritized by PO

37
Q

Why is changing sprint durations throughout the year a bad idea?

A

Prevents the team from establishing velocity. Without a velocity, the team will not be able to plan releases

Prevents the team from establishing predictability. Without an established sprint duration the team can never reach highly accurate predictions

38
Q

How often should code be integrated?

A

Daily

39
Q

How can we ensure that code is integrated daily?

A

Set continuous integration standards as part of the DOD

40
Q

What might an increase in escaped defects mean?

A

An increase in the number of escaped defects or defects, in general, can indicate issues with development and test processes. The team should review the processes to determine how to improve them.

41
Q

What should be in place before Sprint planning?

A

Product Vision
Product Roadmap
Well written user stories that are properly estimated
A prioritized Backlog

Programming (80 decks)

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