Planning,Monitoring and Adapting

Question 1

reviews

Answer 1

reviews

Question 2

Kanban board as information radiator

Answer 2

1) Kanban board
2) Burndown charts
3) Parking lot charts
4) Calendars

Question 3

timeboxing

Answer 3

Core aspect of rapid application development (RAD) software development processes such as dynamic systems development method (DSDM) and agile software development.

Question 4

Advantages of iteration

Answer 4

1) Velocity can be measured and scope can be adjusted quickly
2) forces work into byte sized chunks where define/build/test cycle has to be concurrent
3) More opportunity to succeed or fail early

Question 5

Challenges with Variance Analysis

Answer 5

Time Delay
Variance Source Information
Standard setting

Question 6

WIP limits

Answer 6

WIP limits

Question 7

burn down charts

Answer 7

1) A burn-down chart tracks how much work remains on your project and whether you’ll hit your deadline.
2) The vertical axis measures work remaining. The horizontal axis marks your iterations

Question 8

cumulative flow diagrams

Answer 8

1) Graphic depiction of how stories are moving through various statuses on the way to being “Done”
2) Total scope of a project, grouped by status, and thus lets us know how much of that scope is in a particular status at a given time

Question 9

backlog grooming/refinement

Answer 9

backlog grooming/refinement

Question 10

product-feedback loop

Answer 10

product-feedback loop

Question 11

Planning initiation concepts

Answer 11

d

Question 12

Planning overview

Answer 12

1) Work is not predictable, so adapt
2) Just in time approach to planning
3) Frequent customer involvement
4) Success linked directly to proper agile planning

Question 13

monitoring overview

Answer 13

all members Responsible
release level and iteration level monitoring
Corrective action implementation
Majority monitoring and iteration level

Question 14

adapting overview

Answer 14

Occurs at all level
Includes all stakeholders
Minimize what isn’t working and optimize what is working
Performed continuously throughout project

Question 15

Project planning initiation tools

Answer 15

1) Project charter
2) Business case
3) Statement of work
4) Project Data Sheet
5) Project Kickoff meeting

Question 16

Project charter

Answer 16

1) Before agile strategic planning
2) Includes how to execute the project
3) Processes not in Organization’s operating procedures
4) Max 2 to 3 pages in length

Question 17

Kanban

Answer 17

1) card or sign
2) standard units or lot sizes with single card attached to each
3) New card is pulled into the system only when the work represented by an “in progress” card is completed

Question 18

Kanban board

Answer 18

1) Visualization tool

2) Use a card as a token of task, feature and stick them to a timeline(board)

Question 19

Burndown charts(kanban)

Answer 19

1) Count the number of Kanbans(backlog task) and track it in a timebox
2) Shows the trend of work accomplished

Question 20

Parking lot charts

Answer 20

Summarize the top-level project status

Question 21

Three viewpoints of Kanban boards

Answer 21

1) Time - Releases to iterations to Days
2) Task - Features to stories to tasks
3) Team - Manager, customers, developers, business analysts, users, testers and other stakeholders

Question 22

Kanban board task

Answer 22

1) A feature is a function useful and meaningful to users
2) A story is a testable piece of a Feature (described in words of users)
3) Task is work unit of story (described in terms used by developers)

Question 23

Why use time boxing

Answer 23

1) Avoid missing windows of opportunity
2) Chunk up a problem
3) Deliver incremental results
4) Defeat analysis paralysis - switch gears from think mode to execution

Question 24

Using Timeboxes effectively

Answer 24

1) Identify candidate areas for time boxing
2) Identify your objectives
3) Identify the appropriate time box
4) Execute results with your time box
5) Evaluate and adapt

Question 25

Identify your timebox objectives

Answer 25

1) Meet a deadline
2) Show incremental results.
3) Make incremental progress on a tough problem.
4) Build momentum.

Question 26

Execute results within your time box

Answer 26

1) Execute within your timebox and stop when you run out of time
2) how to stay completely focused
3) how to treat time as a limited resource, 4) how to tune your results.

Question 27

Iteration planning

Answer 27

1) selects and reviews the stories for the current iteration
2) defines and estimates the tasks necessary to deliver the increment of work
3) tasks are typically estimated in “ideal developer days” or even hours
4) details of the requirements are discussed and negotiated

Question 28

Iteration Planning Guidelines

Answer 28

1) first day of the iteration, first thing in the morning. no more than 4 hours.
2) Create task estimates for each story on the basis of ideal effort hours, or points
3) at least one story with a demonstrable function included in the iteration
4) if a story breaks out into seven or more tasks, consider splitting the story.
5) Once the iteration is underway, no change requests by the product manager are allowed

Question 29

Agile Release Planning

Answer 29

1) Small releases are better
2) They provide a constant flow of shippable product increments and generate regular feedback from the end-users
3) The logistics and overheads of releasing need to be minimized

Question 30

Purpose of Agile Release Planning

Answer 30

A goal for the release.
A prioritized set of stories that will be developed in the release.
A coarse estimate for each story.
A date for the release.

Question 31

Preparing for the Release Planning Meeting

Answer 31

1) Define a goal for the release
2) Produce a prioritized wishlist of stories for the release
3) Time permitting, have some developers preview the wishlist to ensure they understand the gist of the stories
4) Review the wishlist

Question 32

Purpose of the Release Planning Meeting

Answer 32

1) everyone in the team understand and commit to delivering the agreed release by the agreed date.
2) The product owner explains the release goal to the team
3) The developers provide their team’s velocity
4) In the order of value, the product owner introduces each story to the developers.
5) The developers ask enough questions
6) The developers assess the technical risk for each story and provide some classification, e.g. high, medium or low.
7) the product owner selects the stories from the wishlist to make up the release plan.
8) Consensus

Question 33

Daily standups

Answer 33

1) What was accomplished yesterday
2) What is planned to accomplish today
3) What issues are blocking progress

Question 34

Goals of daily standups

Answer 34

GIFTS (Good start, Improvement, Focus, Team, Status)
To help start the day well
To support improvement
To reinforce focus on the right things
To reinforce the sense of team
To communicate what is going on

Question 35

Burn up charts

Answer 35

1) A burn-up chart tracks how much work is done.

2) Line showing how much work is in the project as whole (the scope as workload), and this can change

Question 36

Overview of Cumulative Flow Diagrams

Answer 36

1) Whether or not value is being delivered as the result
2) Are stories reaching the final status?
3) Where the bottlenecks are in our workflow
4) How long it takes something of value to be produced
5) Whether the scope of a project is changing

Question 37

Burndown chart vs Cumulative flow diagram

Answer 37

1) Outstanding work at a particular time vs how we are doing in terms of delivering value
2) The cumulative flow graph is not bound by sprint boundaries

Question 38

Kanban cumulative flow diagram items

Answer 38

1) Backlog
2) Priority 3
3) Priority 2
4) Priority 1
5) Working
6) The Pen
7) Complete
8) Archive

Question 39

Downsides of Cumulative Flow Graph

Answer 39

1) The CFG is information dense, so it is harder for a beginner to understand and interpret.
2) CFGs are a lot harder to maintain by hand

Question 40

Intraspective

Answer 40

1) similar to retrospective
2) Discussion of issues
3) determine needed process changes
4) Intra -> with in (during the sprint)

Question 41

agile discovery

Answer 41

1) find what customer want
2) Listening - build an understanding by listening to customer
3) interacting up front
4) gaining clarity

Question 42

discovery team

Answer 42

1) PO put together a team
2) progressive elaboration => user story
3) Continuous customer engagement
4) requirements handed off to delivery team
5) discovery continues

Question 43

agile req review

Answer 43

1) backlog grooming

2) no formal requirements signoff

Question 44

Agile tools

Answer 44

1) learn and grow
2) collaboration games
3) 5 whys
4) intraspective meeting

Question 45

Collaboration

Answer 45

1) leader is not necessary
2) members are responsible and accountable
3) trust and respect

Question 46

Collaboration games

Answer 46

1) having fun and learning
2) build rapport and accountability
3) structured activities
4) improved understanding ownership and relationships
5) eg. the broken telephone, human knot, one word story telling

Question 47

Intraspective explained

Answer 47

1) Scrum master (PO not involved)
2) Held as necessary
3) discuss issue and to identify solution