Yay or Nay Flashcards
User stories are tools used in agile to capture a description of a feature from the end user’s perspective.
Yay
Stakeholder perspective / requirement
User stories are only written by the product owner
Nay
Team members can also write them
A good user story is independent, valuable and complex
Nay
I.N.V.E.S.T.
Agile is for software development teams
Nay
Can be applied to other areas of the organization
Agile is based on systems thinking
Nay
Lean is based on systems thinking
Disciplined Agile applies design thinking
One of the DA principles is “be cool”
Nay
Be awesome or Be pragmatic
Instead of prescribing best practices, DA provides strategies for maximizing the benefits of agile
Yay
Process goals and decision points - no best practices
You can take control of your processes if you don’t know what your options are
Nay
Need to know options and trade-offs
You can’t necessarily understand the behavior of a complex adaptive system by understanding its individual parts
Yay
Need to understand interaction of individual parts
A DA Enterprise responds swiftly to changes in the marketplace
Yay
Business agility is built into the enterprise
The foundation layer includes DAD and other enterprise aspects of Dev Ops
Nay
DA Dev Ops is another layer
DA addresses all possible roles that will occur in an organization
Nay
Roles vary across organizations
A person may take on several roles in parallel
Yay
Multiple hats common for smaller teams/organizations
There is no room for managers in DA
Nay
Managers can be stakeholders or hold supporting role
Cross-functional, “whole” teams enable agility
Yay
“Whole” teams include team members with the skills to address the problem that it faces
Agile teams must be small and co-located
Nay
Depends on context
Co-located teams should have a dedicated workroom
Yay
Ideal situation, but not prescriptive
Members of a collaborative enterprise team become members of a work team
Nay
Not always - however, it is an option
Business agility is sometimes referred to as enterprise agility
Yay
It is possible to understand a complex adaptive system by understanding the individual parts
Nay
Complex adaptive systems cannot be understood just by understanding the individual parts
The agile lifecycle requires a mature set of practices around continuous integration and continuous delivery
Nay
This applies to Continuous Delivery: Agile life cycle
The lean lifecycle is a Kanban-based project life cycle
Yay
Lean is Kanban-based
Agile is Scrum-based
A value stream begins with a great idea
Nay
Value stream begins and ends with the customer
Value is realized when customer pays for the service
Nay
Value is defined by the customer
Minimum business increments are about building something quickly to demonstrate to the product owner
Nay
MBI is to build the smallest enhancement to an existing product - for revenue
MVP is take the smallest step to determine viability of a new product without a customer base - for discovery
Benefits of MBI include adding value to the customer and providing feedback that the right functionality is being built and can be validated as useful
Yay
MBIs should be sequenced in order of priority
Nay
Sequence MBI in order of what can realize the most value more quickly than others
Hand-offs are a way to eliminate waste and delays
Nay
Hand-offs add to waste/delay
“Five Whys” analysis focuses on the tasks and processes within one phase that contribute to waste
Nay
Continuous validation required to build quality in
Delays are a major form of waste in software development
Yay
Using pull is a way to manage workflow in the face of uncertain timing for getting tasks done
Yay
Pulling work when we are ready allows us to manage our own workload level
Kanban boards can provide much of the information that value stream maps do
Nay
Kanban boards depicts the team’s high-level process in terms of state
Value stream map depicts processes, the time spent performing them, the time taken between them, and the level of quality resulting from processes - Used to explore the effectiveness of existing processes and to propose improved ways of working
Attendance in communities of practice is mandatory
Nay
Voluntary
Centre of excellence is often referred to as a guild
Yay
An organization may have serval communities of practice and several centers of excellence at the same time
Yay
“Context counts” is a Lean principle
Nay
Context counts is a DA principle
Lean seeks to optimize the whole value stream, not just individual functions and teams
Yay
