L3 - Agile in Theory

Question 1

problems with traditional waterfall methodology (5)

Answer 1

1. late testing and feedback
2. inflexibility to change
3. risk of misalignment with customer needs
4. long development cycles
5. limited collaboration

Question 2

processes and tools less important than?

Answer 2

individuals and interactions

Question 3

comprehensive documentation less important than?

Answer 3

working software

Question 4

contract negotiation less important than?

Answer 4

customer collaboration

Question 5

following a plan less important than?

Answer 5

responding to change

Question 6

non-project example of agile

Answer 6

agile includes any collaborative/supportive/non-hierarchical relationships that empower users and embrace change fall in this category

eg. the principles of feminine economy

Question 7

core concepts of agile (7)

Answer 7

1. epic and user stories
2. product backlog
3. burndown chart
4. minimal viable product (mvp)
5. velocity
6. batch size
7. estimation

Question 8

define epic

Answer 8

large bodies of work that can be broken down into number of smaller tasks (stories)

Question 9

define stories

Answer 9

also ‘user stories’
–> short requirements or requests written from the perspective of an end user

Question 10

I.N.V.E.S.T - user stories

Answer 10

I - independent
N - negotiable
V - valuable
E - estimable
S - small
T - testable

Question 11

define product backlog

Answer 11

comprehensive product ‘to do’ list

Question 12

where does the PB come from?

Answer 12

product roadmap - strategic document/plan of action for how a product/solution will evolve over time outlining future product functionality + when new features will be released

Question 13

what could be included in a PB? (3 examples)

Answer 13

1. user stories
2. features
3. bug fixes

Question 14

define burndown chart

Answer 14

graphical representation of work left v time left

vertical axis –> outstanding work
horizontal axis –> remaining time

Question 15

burndown chart applications (4)

Answer 15

1. predicting when work will be completed
2. simple/easy to track daily progress of team
3. allows problems to be seen early
4. visually represents problems in software development

Question 16

define MVP

Answer 16

minimal viable product
–> version of product with just enough features to be usable by early customers
–> can then provide feedback for future product development

Question 17

define velocity

Answer 17

velocity = units of work (user stories) completed in given time frame (iterations/sprints/weeks)

Question 18

application of velocity example

Answer 18

works out how much can be completed in each iteration –> creates accurate and efficient timelines

Question 19

define batch size

Answer 19

number of items that will be worked on in one sprint + the total amount of WIP (work in process)

Question 20

what does a large batch size lead to? (3)

Answer 20

1. longer sprints
2. slower adaptation
3. holding cost

Question 21

what does a small batch size lead to? (3)

Answer 21

1. faster and more sprints
2. more deployment costs
3. transaction cost

Question 22

holding cost

Answer 22

the bigger the batch, the more component parts, and more relationships between component parts

Question 23

transaction cost

Answer 23

must reduce transaction cost by increasing transparency, making communication easier and automating/hardening processes

Question 24

features used in agile estimation (5)

Answer 24

1. business value
2. done at a user story level
3. units are story points
4. are relative so no absolute time prediction
5. can be/are revised in every iteration

Question 25

how is agile estimation counted?

Answer 25

fibonacci sequence
–> easier to estimate when smaller