Agile Principles and Mindset

Question 1

Agile Manifesto - 4 Values

Answer 1

Individual and Interactions over processes and tools;
Working Software over comprehensive documentation;
Customer Collaboration over contract negotiation:
Responding to Change over following a plan.

Question 2

Agile Principles - Customer Satisfaction

Answer 2

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software

Question 3

Agile Principles - Change

Answer 3

Welcome changing requirements, even late in development, Agile processes harness change for the customer’s competitive advantage.

Question 4

Agile Principles - Deliver frequently

Answer 4

Deliver working software frequently, from a couple of weeks to a couple of months, with preference to the shorter timescale

Question 5

Agile Principles - Collaborate with business

Answer 5

Business people and developers must work together daily throughout the project

Question 6

Agile Principles - Motivate people

Answer 6

Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

Question 7

Agile Principles - Face-to-Face communication

Answer 7

The most efficient mothed of exchanging information to and within a development team is face-to-face communication

Question 8

Agile Principles - Working software

Answer 8

Working software is the primary measure of progress. If it’s not tested, it’s not measured.

Question 9

Agile Principles - Sustainable pace

Answer 9

Agile processes promote sustainable development, The sponsors, developers and users should be able to maintain a constant pace indefinitely.

Question 10

Agile Principles - Tech and design excellence

Answer 10

Continuous attention to technical excellence and good design enhance the agility

Question 11

Agile Principles - Simplicity

Answer 11

Simplicity - the art of maximizing the amount of work not done - is essential

Question 12

Agile Principles - Team creates architecture

Answer 12

The best architecture, requirements and design emerge from self-organising teams.

Question 13

Agile Principles - Reflect and Adjust

Answer 13

At regular intervals, the team reflects on how to become more effective, then tunes and adjust its behaviour accordingly.

Question 14

Scrum 3 pillars

Answer 14

Transparency; Inspection; Adaptation

Question 15

Scrum 5 values

Answer 15

Focus; Courage; Openness; Commitment; Respect

Question 16

Scrum Roles

Answer 16

Development Team; Scrum Master; Product Owner

Question 17

Scrum Ceremonies

Answer 17

Planning; Daily standups; Sprint review (Demo); Sprint Retrospective; Backlog Refinement

Question 18

Scrum Artifacts

Answer 18

Product Increment; Product Backlog; Sprint Backlog

Question 19

Scrum Master

Answer 19

Servant Leader who: Coaches the team/company to ensure Scrum methodology is understood and properly applied; removes impediments for dev team; facilitates events; assists PO with backlog;

Question 20

XP 5 Core Values

Answer 20

Simplicity; Communication; Feedback; Courage; Respect

Question 21

XP 4 team roles

Answer 21

Coach; Customer; Programmer; Tester

Question 22

XP Core Practices: Whole team

Answer 22

All contributors are in the same room; Anyone who is qualified to perform a role, can undertake it;

Question 23

XP Core Practies: Planning Games

Answer 23

Release planning - what will be pushed to live. 1-2 times a year. Customer priorities; Devs estimate high level.
Iteration planning - short cycle in a release. Customer selects the functionality, Devs estimate more refined and commit to finish the work.

Question 24

XP Core Practices: Small Releases

Answer 24

Frequent small releases to test env. Rigorous Testing. Continuous integration.

Question 25

XP Core Practices: Customer Tests

Answer 25

Acceptance Criteria; Automated tests.

Question 26

XP Core Practices: Collective Code Ownership

Answer 26

Multiple people will work on all the code; All are responsible for the code; All can do changes.

Question 27

XP Core Practices: Code Standards

Answer 27

Help to maintain quality and the same style of code; Consistency

Question 28

XP Core Practices: Sustainable Pace

Answer 28

Ensures high productivity long term; No burndowns; Optimization of the delivery long-term

Question 29

XP Core Practices: Metaphor

Answer 29

Metaphors for explaining to non-tech stakeholders; Designs are metaphors; Common set of names for the elements

Question 30

XP Core Practices: Continuous Integration

Answer 30

Integration and building at each commit; Ensures nothing breaks; Auto-run of integration tests.

Question 31

XP Core Practices: Test-Driven Development

Answer 31

Write test-Run test-Fail-Write code-Run test-Pass

Question 32

XP Core Practices; Refactoring

Answer 32

Improving design of existing code, without altering system’s behaviour

Question 33

XP Core Practices: Simple Design

Answer 33

Keep it simple but adequate, then improve. What is the simplest thing that could work?
Simple design is a risk mitigation strategy.

Question 34

XP Core Practices: Pair Programming

Answer 34

One is writing, second looking, then exchange roles. Larger knowledge base; no bus effect; catch issues early

Question 35

Lean 3 high level principles

Answer 35

Using visual tools;
Identifying customer-defined value;
Building in learning and continuous improvement;

Question 36

Lean 7 Core Concepts

Answer 36

Eliminate waste; Empower the team; Deliver fast; Optimize the whole; Build quality in; Defer decisions; Amplify learning

Question 37

Lean 7 waste types

Answer 37

Partially done work; Extra processes; Extra features; Task switching; Waiting; Motion; Defects

Question 38

Kanban 5 Principles

Answer 38

Visualize the workflow; Limit WIP; Manage flow; Make process policies explicit; Improve collaboratively