Agile Principles and Mindset Flashcards by Mirco Stoffel

What are the two strategies to fulfil agile values and principles?

a) adopt a formal agile approach

b) implement changes in a manner that fits the context and serves the value

How well did you know this?

Not at all

Perfectly

Industrial vs. Knowledge Work

Industrial -> Upfront planning is required (Task driven, command and control)
Knowledge -> expects change and is invisible work (Value driven, autonomy of individuals)

How well did you know this?

Not at all

Perfectly

Empirical vs. Defined Processes

Defined -> works always the same way

Empirical -> observe and react on results of the work

How well did you know this?

Not at all

Perfectly

6 Declaration of Interdependence (DoI) Rules

and Agile Leadership Network

1 -> Increase ROI
2-> Deliver reliable results
3-> expect uncertainty
4-> unleash creativity and innovation
5-> boost performance
6-> improve effectiveness and reliability

How well did you know this?

Not at all

Perfectly

Agile Core Principles

1 -> Welcome and expect change
2-> create small value-added increments
3-> Utilize feedback loops
4-> learn through discovery and creativity
5-> Focus on value for stakeholders
6-> Fail and learn fast
7-> deliver value
8-> improve upon the project/work

How well did you know this?

Not at all

Perfectly

Inverted Triangle Model

Normal -> Time, Costs vs. Scope

Agile-> Time and Costs are Fixed and Scope varies

How well did you know this?

Not at all

Perfectly

Organizational Agility Concept

Person > Team&raquo_space; Organization -> Start with one and increase throughout the organization

How well did you know this?

Not at all

Perfectly

Difference between doing vs. being Agile

Doing -> Knowing the terms

Being -> having the mindset

How well did you know this?

Not at all

Perfectly

Agile Manifesto - The four Values

1-> Individuals and Interactions over (>) processes and tools (focus on People first)
2-> Working Software over (>) comprehensive documentation (focus on business need)
3-> Customer collaboration over (>) contract negotiation (focus on change)
4-> Responding to change over (>) following a plan
(focus on progress not perfection)

How well did you know this?

Not at all

Perfectly

12 Principles of Agile

1-> early and continuous delivery of software
2-> welcome change even late in development
3-> deliver in short timeframes
4-> business and developer work together
5-> empower the team give
6-> face-to-face works better
7-> working software is progress
8-> agile is sustainable (just enough work)
9-> attention to technical excellence
10-> simplicity - what you don’t do is essential
11-> self organizing team
12-> reflect and adjust to become more effective

How well did you know this?

Not at all

Perfectly

4 Project Lifecycles

a) Predictive -> Fixed Requirements -> Single Delivery -> Manage Cost
b) Iterative-> Dynamic Requirements -> Single Delivery -> Correctness
c) Incremental -> Dynamic Requirements -> Frequent Delivery -> Speed
d) Agile -> Dynamic Requirements -> Frequent Delivery -> Customer Value

How well did you know this?

Not at all

Perfectly

Scrum Pillars and Values

1->Transparency
2->Inspection
3->Adaptation

How well did you know this?

Not at all

Perfectly

Scrum Sprints in Detail

1-> Timboxed (1-4 Weeks)
2-> no changes that affect the goal of the sprint
3-> only product owners can cancel a sprint

How well did you know this?

Not at all

Perfectly

Scrum Sprint activities

1-> planning meeting
2-> development
3-> daily scrums
4-> review meeting
5-> retrospective meeting

How well did you know this?

Not at all

Perfectly

Scrum Roles

1-> Scrum Master
2-> Product Owner
3-> Development Team

How well did you know this?

Not at all

Perfectly

Scrum Artifacts

1-> Product Increment
2-> Product Backlog
3-> Sprint Backlog

Extreme Programming XP

Includes Pair Programming and has the following phases: Exploration -> Iteration Planning -> Iteration -> Customer Approval -> Small Release

Important Components/Values of XP

1->Collaboration
2->Feedback
3->Courage
4->Respect

4 XP Roles

1->Coach
2->Customer
3->Programmer
4->Testers

XP Core Practices

1->Planning Games
2->Small Releases
3->Customer Tests
4->Collective Code Ownership
5->Code Standards
6->Sustainable Pace
7->Metaphor
8->Continuous Integration
9->Test-driven development
10->Refactoring
11->Simple Design
12->Pair Programming

7 Lean Core Concepts

1->Eliminate waste
2->Empower the Team
3->Deliver fast
4->Optimize the whole
5->Build quality in
6->Defer decisions
7->Amplify learning

7 wastes of Lean

1->Partially done work
2->Extra processes
3->Extra features
4->Task switching
5->Waiting
6->Motion
7->Defects

DSDM (Dynamic System Dev. Method)

1->Focus on the business need
2->Deliver on time
3->Collaborate
4->Never compromise quality
5->Build incrementally from foundations
6->Develop iteratively
7->Communicate continuously and cleary
8->Demonstrate control

Feature Driven Development

1->Model of the Product
2->Build a feature list
3->Design the feature
4->Build the Feature

What is Crystal

1 -> Flavor of Agile coded by color names 2-> Colors are linked to criticality 3-> Crystal clear, crystal yellow, crystal orange, etc. 4-> Each color indicates also different tailoring of processes, policies and practices

Agile Project Management

1 -> Product Vision (Aligned with Company's strategy) 2-> Product Roadmap (product releases) 3-> Release Planning (Product backlog) 4-> Iteration Planning (Spring planning) 5-> Daily Scrum (15min, done, do, impediments) 6-> Sprint review (demo of the product) 7-> Sprint retrospective (lessons learned) 8-> Released Product

Roles in Agile

1-> Cross-functional team members 2-> Product owner 3-> Team facilitator (hub of communications)

Agile - Cross-Functional Teams are critical because:

1-> They can deliver finished work in the shortest possible time 2-> with higher quality 3-> Without external dependency

Management vs. Leadership

Management -> get things done | Leadership-> Empowerment, direction, principles

Agile - Product Owner tasks

1-> guide the direction of the product 2-> rank the work based on business value 3-> provide feedback 4-> Set direction of the next iteration

Agile - Team Facilitator

Servant Leader

Servant Leadership Concept

=> Purpose -> People -> Process 1-> Self-awareness 2-> Listening 3-> Serving the team 4-> Help people to grow 5-> coaching vs. controlling 6-> Promoting safety, respect & trust 7-> Promoting energy and intelligence of others => It's all about building relationships, facilitate collaboration, remove impediments.

Leadership Tasks

1-> Give transparency through visualization 2-> Create save environment for experiments 3-> Experiment with new techniques and processes 4-> Share knowledge through collaboration

Team Environment / Team Stages

Forming -> Storming -> Norming -> Performing | -->> Adjourning

Agile Teams

- > 3-9 members - > One Team space - > 100% dedicated - > Self managed teams

Osmotic Communication

-> Is a benefit of co-located teams because you hear and understand what is going on around you

Emergent Leadership definition

1-> Team success over (>) individual success 2-> anyone can be a leader 3-> understanding roles and responsibilities -- 4-> Allow members to take charge 5-> Motivate members 6-> show recognition of individuals and team 7-> Avoid zero sum reward (only 1. person can win the reward)