Agile Practice- Chapter 3 Flashcards

1
Q

Life Cycle Selection

A

Approach used based on the project

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

Predictive Life Cycle

A

Traditional approach with the bulk of the work done upfront, then executing in a single pass; Activities performed in a single pass

There can be projects with a predominantly predictive approach with some elements of agile.
Example- An engineering firm that is building a facility with a new component. The majority of the project is routine and predictable; incorporating a new component (roofing material) would mean an agile approach (iterative) to test the roofing material

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

Characteristics of Predictive Life Cycle
(Non-Agile Approach)

A
  1. Low risk
  2. Stable Team
  3. Requirements are firm
  4. Single Delivery
    Goal- Manage Cost
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Predictive Life Cycle Model

A

Analyze-Design-Build-Test-Deliver

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

Iterative Life Cycle- Flow

A

Allows feedback for unfinished work to improve and modify that work; it allows feedback on partially completed or unfinished work

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

Characteristics of Iterative Life Cycle

A
  1. Improve the product or result through successive prototypes or proofs of concepts
  2. Each prototype yields stakeholder feedback and team insights
  3. Team incorporates new information by repeating one or more projects into the next cycle
  4. High complexity projects
  5. Frequent changes
  6. Scope is subject to differing stakeholder’s views of the final project
  7. Takes longer
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Iterative Life Cycle- Flow

A

Analyze- Analyze Design (Prototype)-Build/Test (Refine)- Deliver

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

Incremental Life Cycle

A

Provides finished deliverables that the customer may be able to use immediately

Increment- A functional , tested and accepted deliverable that is a subset of an overall project

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

Incremental Life Cycle Characteristics

A

1 Performed once for a given increment
2. Frequent smaller deliveries
3. Optimizes work by delivering value to sponsors/customers more often than a single final product
4. Plan initial deliverable before beginning their work and they begin work on that first delivery as soon as possible

Goal- Speed; businesses can’t afford to wait until everything is finished. Customers are willing to receive a subset of the final project.

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

Incremental Life Cycle-Flow

A

Analyze Analyze Analyze
Design Design Design
Build Build Build
Test Test Test
Deliver Deliver Deliver

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

Agile Life Cycle

A

An approach that is both iterative and incremental to refine work items and deliver frequently

Agile approaches can have predictive components.

Example- A particular element is non-negotiable or not executable using an agile approach. Integrating an external component developed by a different vendor that can’t or will not partner in an incremental way. Especially if a single integration is required.

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

Agile Life Cycle Characteristics

A
  1. Repeated until correct
  2. Frequent small deliveries
  3. Iterate over the product to create finished deliverables
  4. Team gains early feedback and provides customer visibility, confidence, and control of the product
  5. Team can release earlier; project may provide early return on investment because the team delivers the highest value work first
  6. Team expects requirements to change
  7. Delivery uncovers hidden or misunderstood requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Agile Iteration Based Life Cycle- Flow

A

Requirements
Analysis
Design
Build
Test

Each timebox is the same size and results in working tested features. The cycle repeats as needed.

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

Agile Flow-Based Life Cycle- Flow

A

Requirements
Analysis
Design
Build
Test

Each timebox is different. In the flow, the time it takes to complete a feature is not the same for each feature. Work in progress (WIP) limits set the amount of work that can exist in a work flow.

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

Assessment Models

A

Exist to help determine the likely fit or gaps for using agile approaches

These should be completed as a group.

Small group should consist of sponsor, technical lead, and customer.

Large group should consist of sponsoring group, project execution team, impacted business groups, governance group, customer community

It is important to follow the consensus.

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

Dynamic Systems Development Method
(DSDM)

A

Questionnaire and organizational suitability to gauge likely fit and problem areas

14
Q

Crystal

A

Ranks projects by size and the criticality of the product or service being developed.
- less critical; smaller projects with lighter controls and simpler approaches
- large mission or life critical projects; use more rigor and validation

15
Q

Agile Approach Assessment

A
  1. Culture- Is there a supportive environment with buy-in for the approach & team trust
  2. Team- Is the team of suitable size to be successful in adopting agile? Is the team experienced? Is there access to business representatives?
  3. Project- Are there high rates of change? Is incremental delivery possible? How critical is the project?
15
Q

Hybrid Life Cycle Examples

A

Campus Construction Project
Incremental Approach- Completing some buildings earlier than others. Each individual delivery may be well known (predictive)

15
Q

Questions that should be asked before determining which approach to use

A
  1. How can we be most successful?
  2. Is feedback necessary as the team produces value?
    (If yes, incremental life cycle)
  3. Is it necessary to manage risk as ideas are explored?
    (If yes, iterative life cycle or agile.)

When the organization can’t deliver intermediate value, agile approaches may not be useful.

16
Q
A
17
Q
A