Introduction To Agile Flashcards

1
Q

What is the Agile Manifesto

A

• Individuals/Interactions over processes & tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Respnding to change over following a plan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What type of thinking is Agile compatible with?

A

Lean

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the 2 main methods within the foundation syllabus?

A

• Scrum
• Kanban

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Is Scrum a project management process?

A

•No it is a type of approach.
•Used as Business as Usual
•Can fit into Prince2

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the only Agile method that is a Project Management Lifecycle and cannot be used in Prince2?

A

DSDM (Dynamic Systems Development Method/Agile PM)

[Cannot be used in Prince2]

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Give a brief description of Kanban

A

• A way to improve flow and provoke system improvement through visualisation and controlling work in progress

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Give a brief description of Lean Start-Up

A

• First used foe startup companies
• To help deliver products to customers quickly

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Give a brief description of Scrum

A

• Iterative time boxed approach to delivery
• Lightweight framework that helps people, teams and organisations generate value through adaptive solutions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

List the typical Agile behaviours

A

• Collaborative
• Self-organising
• Customer-focused
• Empowered
• Trusting not blaming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

List the typical Agile concepts

A

• Prioritising what is delivered
• Working iteratively & incrementally
• Not delivering everything
• Time-focused
• Inspect and adapt
• Kaizen
• Limiting Work in Progress

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

List the typical Agile Techniques

A

• Burn Charts
• User Stories
• Retrospectives
• Time boxing
• Measuring Flow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is a backlog?

A

• A to-do list
• Contain requirements:
- Contain EPICS (at highest level)
- Contain user stories

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is velocity?

A

Progress against the sprint/timebox

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What can Scrum help with in projects?

A

• Create a team
• Building solutions/products

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is a sprint?

A

A period of time dedicated to a single objective

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the key things to be created in scrum?

A

• Creation of team
• Creation of a backlog (Product BL & Sprint BL)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Summarise the Scrum method

A

• A creation of a Product Backlog (EPICS and user stories)
• Creation of the development team
• DT creates a sprint backlog of a certain no. of EPICS & User Stories to work on
• Daily Scrum meetings in each sprint
• After each sprint there is a sprint review and sprint retrospective

18
Q

What people are involved in the Scrum team?

A

• Product Owner (Liaising with customer translates user stories/epics into backlog)
• Develoment Team
• Scrum Master (Help all members to work better)

19
Q

Is there a project manager in scrum?

A

• No
• Scrum is not a project management process
(No leader at all)

20
Q

What is the likely number of people in the Development Team?

A

• 3-9 people

21
Q

What is involved in a sprint review?

A

• Demonstrate achievements to stakeholders
• Allow to adapt to change if requested by stakeholder for next sprint

22
Q

What is a sprint retrospective?

A

• Plan ways to increase quality & effectiveness for next sprint
• Scrum team reviews last sprint (Individuals, processes, interactions & tools)
• Identifies helpful changes

23
Q

What are the 5 Scrum events?

A
  1. Sprint Planning
  2. The Sprint
  3. Daily Scrum
  4. Sprint Review
  5. Sprint Retrospective
24
Q

What creates the Sprint Backlog

A

• The development team and their Sprint Planning Meeting

25
Q

What are Scrum Artefacts?

A
  1. Product Backlog (High level objectives - EPICS & User St)
  2. Sprint Backlog (Creation of work from Prod Backlog to achieve individual objective)
  3. Increment - A block of sprints/work to create a definition of done for a stepping stone towards the product goal
26
Q

Summarise a Kanban Board.

A

• Used to create an information radiator
• Normally divided into 3 categories:
- To Do
- Work in Progress
- Done

• Optional additional category of Testing/Verify

• Aids in Definition of Ready
• Aids in Definition of Done

27
Q

In a Kanban Board, what is the “Definition of Ready”?

A

• Something is ready to move into next workstream
• Pieces of work ready to be deployed

28
Q

In a Kanban Board, what is the “Definition of Done”?

A

• A piece of that has been tested and deployed

29
Q

In a Kanban Board, what are Working Progress Limits (WIP)

A

• Work started but not delivered from system.
• For example because a restricted No. of people available ie. in the build workstream or Deployment workstream.
• Can indicate status for incidents, problems, changes etc.

30
Q

What problem does Lean Start-Up Address from the project management process?

A

• The changing of customer requirements towards the end of the stage

31
Q

What are the features of Lean Start-Up?

A

• Build, measure learn (Ready, Fire, Aim)
• Create a minimum viable product
• Fail Fast
• Validated Learning

32
Q

What is the Prince2 Agile/ Lean Start-Up version of a Minimum Viable Product?

A

• A version of the final product allowing maximum amount of validated learning with the least effort.
• Delivered as early as possible
• The purpose is learning and may not be used.
• eg. Prototype or experiment

33
Q

What are the testers of MVPs called?

A

Early Adopters
Beta Testers
User Acceptor Testers
Focus Groups

34
Q

Summarise the lifecycle of Lean Start-Up.

A
  1. Leap of faith (Choose to build MVP not wait to end of project to handover)
  2. What makes a successful product?
  3. Build MVP (Prototype)
  4. Offer to early Adopters
  5. Measure success by validated learning
  6. Hypothesise & experiment to improve product
  7. Measure success by validated learning
    -7a. If successful put into mainstream
    -7b. If not hypothesise & experiment again
    Or pivot and try a new leap of faith
35
Q

Where can Kanban, Scrum & Lean Start-Up fit in the Prince2 processes?

A

Managing Product Delivery

36
Q

What Agile Way of Working could be used to effectively address large amounts of work packages in a stage?

A

Kanban Board

37
Q

Who can attend the daily Scrum meeting?

A
  • Development Team
  • PM & Project can observe but not interfere
38
Q

Agile was first created when?

A

1995

39
Q

What does Agile put a lot of emphasis on?

A

Planning

40
Q

What describes the relationship between “cause and effect” of events and interactions?

A

Cynefin

Its a framework to help understand the complexity of a project. If X happens and results in Y, what is the relationship

Used in start up

5 Relationships:
- Obvious
- Complicated
- Complex
- Chaotic
- Disorder

• Used to assess output, outcome or benefit
• Used to assess project environment
• Collaboratively assessed

41
Q

Which communication channel is favoured as a faster channel in Agile?

A

Verbally face-to-face