Basics Flashcards
1
Q
DA Principles (8)
Hint: C.O.D.E.B.O.B.
A
- Delight customers
- Be awesome
- Context counts
- Be pragmatic
- Choice is good
- Optimize Flow
- Organize around products/services
- Enterprise awareness
Combination of Agile + Lean
Agile - started in software development
Lean - started in manufacturing
Principles provide a philosophical foundation for business agility. They are based on both lean and flow concepts.
2
Q
Life Cycles (7)
A
- Agile
- Continuous delivery: Agile
- Lean
- Continuous delivery: Lean
- Exploratory
- Program
- DA FLEX
3
Q
Process Blades (4)
A
- Foundation
- Disciplined Dev Ops
- Value Stream
- Disciplined Agile Enterprise
4
Q
Process Phases (3 + 1)
A
- Inception
- Construction
- Transition
Ongoing - not a phase
5
Q
Inception Process Goals (8)
Hint: F.A.D.E.D.S.I.P.
A
- Form team
- Align with enterprise direction
- Explore Scope
- Identify architecture strategy
- Plan the release
- Develop test strategy
- Develop common vision
- Secure funding
6
Q
Construction Process Goals (5)
Hint: I.P.A.P.A.
A
- Prove architecture early
- Address changing stakeholder needs
- Produce a potentially consumable solution
- Improve Quality
- Accelerate value delivery
7
Q
Transition Process Goals (2)
A
- Ensure production readiness
2. Deploy the solution
8
Q
Ongoing Activities (6)
Hint: C.A.L.E.G.G.
A
- Grow team members
- Coordinate activities
- Evolve WoW
- Address risk
- Leverage and enhance existing infrastructure
- Govern delivery team
9
Q
Inception Milestones - Agile Life Cycle (1)
A
- Stakeholder vision
10
Q
Construction Milestones - Agile Life Cycle (3)
A
- Proven Architecture
- Continued viability
- Sufficient functionality
11
Q
Transition Milestones - Agile Life Cycle (2)
A
- Production ready
2. Delighted customers
12
Q
DA Mindset (3)
A
- Principles
- Promises
- Guidelines
13
Q
Agile Ceremonies (4)
A
- Iteration Planning
- Daily Coordination Meeting
- Iteration Demonstration
- Iteration Retrospective
14
Q
Agile Artifacts (4)
A
- Product Backlog
- Iteration Backlog
- Burndown Chart
- User Story
15
Q
DAD - Primary Roles (5)
A
- Stakeholder
- Team Lead
- Team Member
- Product Owner
- Architecture Owner
16
Q
DAD - Supporting Roles (5)
A
- Specialist
- Independent Tester
- Domain Expert
- Technical Expert
- Integrator
17
Q
DAD - Leadership Roles (3)
A
- Team Lead (Build the product fast)
- Product Owner (Build the right product)
- Architecture Owner (Build the product right)
18
Q
Steps for choosing WoW (5)
A
- Analyze the context
- Select the best-fit life cycle
- Connect the dots
- Make some choices
- Guided Continuous Improvement
19
Q
Disciplined Agile Manifesto (5)
A
- Individuals and interactions over processes and tools
- Consumable solutions over comprehensive documentation
- Stakeholder collaboration over contract negotiation
- Responding to feedback over following a plan
- Transparency over false predictability
20
Q
MVP
A
- Minimum Viable Product
- MVP is take the smallest step to determine viability of a new product without a customer base
- Investment for discovery
21
Q
MBI
A
- Minimum Business Increment
- MBI is to build the smallest enhancement to an existing product
- Investment for revenue
Steps:
a. Determine your audience
b. Decide on the scenario
c. Focus on the smallest amount of value
22
Q
Technical debt
A
Refers to the implied cost of future refactoring or rework to improve the quality of an asset to make it easy to maintain and extend
23
Q
Acceptance Criteria
A
- Unique for each user story
- Motivates team to think through quality-focused requirements (for BDD or ATDD)
- Relying on acceptance criteria alone risks missing details
24
Q
Definition of Done
A
- For all user stories
2. An agreed upon set of items (checklist) that must be satisfied before a user story can be considered complete
25
LEAN Principles (8)
1. Eliminate waste
2. Build-in quality
3. Create knowledge
4. Defer commitment
5. Deliver quickly
6. Respect people
7. Optimize the whole
8. Enterprise aware
26
Agile Lifecycle
Based on Scrum - multi-week iterations
Team type: Project
When to use: Teams new to agile
Disadvantage: Falls apart when requirements change often
Phases:
1. Inception (1 milestone)
2. Construction (3 milestones)
3. Transition (2 milestones)
27
Lean Lifecycle
Based on Kanban - NO iterations
Team type: Project
When to use: New teams with fast evolving requirements
Disadvantage: Requires greater skill and discipline
Phases:
1. Inception (1 milestone)
2. Construction (3 milestones)
3. Transition (2 milestones)
28
Continuous Delivery: Agile Lifecycle
Natural progression from Agile lifecycle
Team type: Product (long-lived)
When to use: Long running teams
Disadvantage: Requires automated regression testing, continuous integration (CI) and continuous deployment (CD)
Phases:
1. Construction (3 milestones)
29
Continuous Delivery: Lean Lifecycle
Natural progression from Lean or Continuous Agile lifecycle (production release several times a day)
Team type: Product (long-lived)
When to use: Long running, disciplined teams
Disadvantage: Requires automated regression testing, continuous integration (CI) and continuous deployment (CD)
Phases:
1. Construction (3 milestones)
30
Exploratory Lifecycle
Based on Lean startup and design thinking
Team type: Experimental/Scientific method
When to use: New product or service offering
Disadvantage: Requires way to target subset of potential customer base
Minimum upfront investments for MVP
31
Program Lifecycle
Enables the organization of a large team of teams
Team type: Project
When to use: Large agile team of teams
Disadvantage: Requires a lot of coordination; hard to scale
Phases:
1. Inception (2 milestones)
2. Construction (3 milestones)
32
Process Goal Diagram Components (5)
1. Process Goal
2. Decision Point
3. Ordered list of options (arrow)
4. Unordered list of options
5. Options in bold are potential starting points
33
Tactical Scaling Factors (7)
| Spider Diagram
1. Team Size
2. Geographic Distribution
3. Organizational Distribution
4. Skills Availability
5. Compliance
6. Solution Complexity
7. Domain Complexity
34
User story characteristics (6)
Hint: I.N.V.E.S.T.
1. Independent (of all others)
2. Negotiable (not a specific contract for features)
3. Valuable (or vertical)
4. Estimable (to a good approximation)
5. Small (so as to fit within an iteration)
6. Testable (in principle)
35
DA Promises (7)
1. Create psychological safety and embrace diversity
2. Accelerate value realization
3. Collaborate proactively
4. Make all work and workflow visible
5. Improve predictability
6. Keep workloads within capacity
7. Improve continuously
Promises are agreements we make with fellow teammates, our stakeholder and other people within our organization. Promises define a collection of disciplined behaviors that enable us to collaborate effectively and professionally.
36
DA Guidelines (8)
1. Validate our learnings
2. Apply design thinking
3. Attend to relationships through the value stream
4. Create effective environments that foster joy
5. Change culture by improving the system
6. Create semi-autonomous self-organizing teams
7. Adopt measures to improve outcomes
8. Leverage and enhance organizational assets
Guidelines help us to be more effective in our WoW and in improving our WoW over time.
37
BDD (Behavior Driven Development)
Synthesis and refinement of practices stemming from Test Driven Development (TDD) and Acceptance Test Driven Development (ATDD).
Applies the “Five Why’s” principle to each proposed user story, so that its purpose is clearly related to business outcomes.
