D1-Agile Principles and Mindset Flashcards
(154 cards)
1
Q
What are the 4 agile values
A
Individuals and interactions over process and tools
Working software over comprehensive documentation
Customer collab over contract neg
Responding to change over following plan
2
Q
What do we value over process and tools?
A
Individual interactions
3
Q
What do we value over comprehensive documentation?
A
Working software
4
Q
What do we value over contract negotiation?
A
Customer collaboration
5
Q
What do we value over following a plan?
A
Responding to a change
6
Q
Our highest priority is to satisfy the customer. How do we do that?
A
Through early and continuous delivery of working software
7
Q
How do agile processes create a competitive advantage?
A
By welcoming changing requirements, even late in development
8
Q
Delivery of working software
A
From a couple of weeks, to months. Shorter timescales
9
Q
Business people and devs must work together…
A
Throughout the project
10
Q
Projects should be build around who? What do they need?
A
Motivated individuals, they need the environment trust and support to get the job done
11
Q
What is the most efficient way to convey information?
A
face to face
12
Q
What is the primary measure of progress?
A
Working software
13
Q
Agile processes and promote what?
A
Sustainable development
14
Q
How do we enhance agility?
A
Continuous attention to technical excellence and good design
15
Q
Simplicity is the art of?
A
Maximizing the work not done
16
Q
What emerges from self organizing teams
A
the best architecture, requirements and design
17
Q
At regular intervals, what does the team do?
A
Reflect on how to become more effective then tunes and adjusts accordingly
18
Q
What practice would help developers find bug?
A
Refactoring
19
Q
What practice can be used to plan out the required user stories for the next increment?
A
Task board
20
Q
What practice can be used to address and find options for reoccurring issues?
A
Retro
21
Q
What practice could be used to ensure a new feature will address the user issues?
A
User Story
22
Q
What practice can be used to better inform of sprint progress?
A
Burndown
23
Q
What practice can developers use to improve code and structure without changing the behavior?
A
Refactoring
24
Q
What practice can be used to track the amount of work left on the sprint or project?
A
Burndown
25
What practice can be used to express a very specific user need
User Story
26
What practice can be used by the team to discuss how they can improve?
Retro
27
What is the most common SW dev approach to agile?
Scrum
28
What agile method focusses on project mgmt?
SCrum
29
What agile method focusses on SW dev?
XP
30
What agile method, focusses on process improvement?
Lean
31
What practice can be used to address changes in what the users might want?
Incremental design
32
What is the most effective way to communicate?
face to face
33
What is the best practice to use to model a typical user?
Persona
34
What is the best way to show team progress?
Demo working software
35
What principle is being practiced when code is built in a way thats easy to change?
Embracing change
36
In KanBan, the teams improve collaborativly and and ______ experimentally
Evolve
37
KanBan focusses on _______ improvement
Process
38
The _________ hold the feature not built yet
Backlog
39
The scrum team demos _______ software
working
40
The scrum team demos for
Users
41
What the scrum team does daily
Daily scrum
42
The Scrum _____ guides the team past roadblocks and helps them implement scrum
Master
43
Who maintains the product backlog in scrum?
THe Product Owner
44
What is the most effective way to communicate?
Fact to face
45
What XP practice helps XP teams make code easy to change?
Incremental design
46
WHat scrum teams do at the start of the project
planning
47
what scrum teams demo at the end of the sprint
review
48
How do scrum teams divide their projects?
Sprints
49
WHat practice helps devs understand who their users are?
Personas
50
This framework focusses on project mgmt and product dev
Scrum
51
What is required to help adopt pratices?
Mindset
52
What ceremony is used to help find lessons learned?
Retro
53
Chart that tracks work left?
Burndown
54
WHat XP team to constantly improve code structure
Refactoring
55
What P teams do with change
embrace
56
A tool or technique used by a team?
Practice
57
What are the 4 values of the manifesto?
Individuals and Int
over
processes and tools
Working Software
over Comprehensive documentation
Customer Collab
over
Contract negotiations
Responding to change
Over
Following a plan
58
When a plan is developed step by step, each new step drawing on knowledge from the previous
progressive elaboration
59
12 agile principles
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business people and developers must work
together daily throughout the project.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Continuous attention to technical excellence
and good design enhances agility.
Simplicity--the art of maximizing the amount
of work not done--is essential.
The best architectures, requirements, and designs
emerge from self-organizing teams.
At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.
60
Setting a hard deadline to complete something
timebox
61
work done by a team to change code to serve a different purpose or function
rework
62
maintained list of feature to be built in the future
backlog
63
developing an artifact in steps,using knowledge gained from the previous step
progressive elaboration
64
team breaks work down into smaller parts
iterative
65
Three pillars of empiricism
transparency, inspection, adaptation
66
6 rules of interdepenance
Increase ROI
Deliver reliable results
Expect uncertainty
Unleash creativity
Boost performance
Improve effectivness
67
What is fixed in agile?
time and cost
68
What varies in agile
scope
69
What is the goal of an incremental approach
speed
70
what is the goal of an agile approach
value
71
what is the goal of an iterative approach?
Correctness of solution
72
Iterative activites are
repeated until correct
73
Incremental activities are
performed once
74
agile activities are
repeated until correct
75
Agile delivery is performed
frequent small deliveries
76
Incremental delivery is performed
frequent small deliveries
77
Iterative delivery is
single delivery
78
WHat should happen before tailoring is considerered
Try OOB, review motivation
79
What are the pillars of scrum?
Transparency inspection and adaptation.
80
What are the scrum roles
PO, SM and Dev Team
81
Scrum is founded on
empiricism and lean thinking
82
Scrum values
commitment, focus, openness, respect, and courage
83
scrum teams are;
cross functional
84
The scrum team size
10 or fewer people
85
Scrum developers are accountable for
creating the sprint plan, instilling quality by adearing to DOD, adapting their plan as required to achieve the sprint goal, holding each other accountable.
86
The PO is accountable for
Creating sprint goal, creating and communicating PBI's, ordering the PBI and ensuring the backlog is transparent visible and understood.
87
The SM in Scrum
coaches team in slef mgmt and cross functionality, helps the team to focus on creating highvalue increments that meet the DOD, removes impediments, ensure scrm events occur and are positive, productive and timeboxed.
88
How does the SM serve the PO
find techniques for product goal def, helps the scrum team understand the need for clear PBI's,establish empirical product planning for complex env and facilitating stakeholder collab
89
How does the SM server the org
leading training the org in scrum adoption, planning and advising on scrum implementation, helping staff enact empirical approach for complex work, removing barriers between stakeholders and scrum teams
90
Scrum events
The sprint, planning, daily, review, retro,
91
Can changes be made during the sprint in Scrum
no
92
Scrum artifacts
PB, SB, Increment
93
What are the artifacts and commitments of scrum
PB= Product goal, SB=Sprint goal,Inc=DOD
94
What are some differences between Scrum and XP?
Scrum teams typically work in iterations (called sprints) that are from two weeks to one month long.
XP teams typically work in iterations that are one or two weeks long.
Scrum teams do not allow changes into their sprints.
XP teams are much more tolerant to change within their iterations, though their iterations are much shorter than Scrum teams' iterations.
Scrum doesn’t prescribe any engineering practices; XP does.
95
Kanban means
Signboard
96
Principles of KanBan
Visualize the flow
Limit WIP
Manage flow
Make process policies clear
Collaborative on improvements
97
Does KanBan use iterations?
No
98
KanBan is a ______ System
Pull
99
True or false Kan Ban uses time boxed iterations
False
100
Kan ban means
Signs you can see
101
Phases of XP
Exploration, Iteration planning, iteration, testing, small release
102
What does XP leverage to ensure quality
Pair programming
103
XP core values
simplicity, communication, feedback, courage,respect
104
XP roles
Coach, Customer, Programmer , tester
105
THe XP team is made up of
generalizing specialists
106
True or false XP teams are remote
False: teams are colocated.
107
What is the max distance team members should be seperated
33ft
108
How many release do we do in XP
1-2 a year
109
What do XP team do to plan
planning games Iteration and release planning
110
_____releases are a core practice of XP
small
111
The core XP practices are
small releases, customer test, collective code ownership, code standards, sustainable pace, metaphor, cont int, TDD, refactoring, simplicity, pair programming
112
Aspects of XP collective code ownership
pair programming, multple people work the code, improve defect resolution, knowledge is shared
113
Aspects of XP code standards
Standard is defined adhered to provide consistency
114
Benefits of refactoring
simpler, easy to understand, adheres to standards
115
The 7 wastes of lean
partially done work
extra processes
extra features
task switching
waiting
motion
defects
116
7 lean core concepts
eliminate waste
empower the team
deliver fast
optimize the whole
build quality in
defer decisions
amplify learning
117
lean was developed at
toyota
118
Characteristics of FDD
Domain object modelling
Develop by feature
individual class code ownership
Feature teams
Inspection
Config mgmt
regular builds
Visibility on progress and results
119
Details of crystals
Colors signal different tailoring depending on the project
120
Product vision must be aligned with what?
Company strategy
121
Product vision is created by the
product owner
122
A visual that represent the product and portions that make up the whole over a period of time
Roadmap
123
What should a roadmap contain
Dev, work, KPI, Dash
124
What is release planning
timing to publish a product feature
125
When is a release pushed to prod
when its ready, could be several sprints
126
Why are cross functional teams critical?
They can deliver faster, with high quality and without external dependencies
127
Servant leadership characterisitics
Promote self awareness
Listening
Serving the team
Help growth
Coaching vs controlling
Promote safety trust, respect
Promoting others
128
Servant leadership responsibilitites
educate stakeholders
support the team
Celebrate the team
Help the Team with PM overhead
129
Agile leadership tasks
information radiator
create safe environment
experiment
share knowledge
130
Characteristics of an agile team
3 - 9 members
located in team space
100% dedicated
self managing
131
Work that is repeatable with clear processes and called ____Processes
Defined
132
Work that is based on experience and observation is called?
Empirical Processes
133
Industrial work relies on
defined processes
134
Knowledge work relies on
Empirical Processes
135
What are the 6 rules of the declaration of interdependence
ROI, Deliver Reliable Results, Expect Uncertainty, Unleash creativity and Innovation, Boost Performance, Improve effectiveness and Reliability.
136
What is ROI
Return on investment - Invest and see a return
137
How do we deliver reliable results?
Testing - UAT, Int testing, Refactoring
138
6 example of the agile mindset
Expect change, create value in small increments, use feedback loops, learn through discovery, focus one value, fail fast, value throughout, CI
139
An approach when introducing agile to a new org or team
demonstrate the value by trying the basics and getting some quick wins and quick ROI
140
What agile approach
141
What is the difference between iterative and incremental?
Iterative=Time box approach to develop vs a continual build of adding features
142
In the agile triangle of constraints, what is fixed and what is variable?
Scope varies. time and cost is fixed.
143
activities in an iterative approach
repeat until correct
144
activities in an Incremental approach
performed once per increment
145
Activities in an agile approach
repeated until correct
146
The goal of an iterative approach
correctness of solution
147
the goal of an incremental solution
is speed
148
the goal of an agile approach
is customer value via frequents feedback and delivery
149
What are the stages of the tuckman model of team formation and development?
Forming, storming, norming, performing adjourning
150
collocated teams should be
33 ft and with no barriers
151
This form of communication occurs when people are close
Osmotic
152
If one person is offsite the team is________
Distributed
153
Examples or digital tools for distributed teams
video conf, interactive whiteboards, IM, virtual card walls
154
This type of leadership means anyone can become a leader
Emergent
