Slide Deck 2 Flashcards

1
Q

What are the four Agile Manifesto things?

A

Individuals and Interactions OVER Processes and Tools

Working Software OVER Comprehensive Documentation

Customer Collaboration OVER Contract Negotiation

Responding To Change OVER Following A Plan

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

What is rapid software development?

A

most important requirement for software systems nowadays. Software has to evolve quickly.

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

What are the 12 principles of agile methods?

A
  1. Satisfy the customer
  2. Welcome change
  3. Deliver working software frequently
  4. Work Together
  5. Trust and Support
  6. Face-to-face communication is best
  7. Working software
  8. Promote sustainable development
  9. Continuous attention
  10. Maintain simplicity
  11. Self-organizing teams
  12. Reflect and Adjust —- Introspection - teams should regularly review itself and its processes to try and improve
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are some problems with agile methods?

A
  • difficult to keep interest of customers who are involved in process
  • team members could be unsuited to the intense involvement of characteristics
  • Changes can be difficult with multiple stakeholders
  • Extra work to keep things simple
  • Contracts could be a problem with iterative approaches
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is plan-driven development?

A

Based around separate development stages with the outputs to be produced at each of these stages planned in advance.

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

plan-driven or agile: is it important to have a very detailed spec and design before moving to implementation?

A

Should user plan-driven approach

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

plan-driven or agile: Is an incremental delivery strategy, where you deliver the software to customers and get rapid feedback from them, realistic?

A

Should use agile methods

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

plan-driven or agile: How large is the system that is being developed?

A

Agile is good for small co-located team, for large teams, plan-driven is the way to go

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

plan-driven or agile: What type of system is being developed?

A

Plan-driven is possibly a must for systems that need a ton of analysis before implementation

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

plan-driven or agile: What technologies are available to support system development?

A

Agile methods rely on good tools to keep track of an evolving design

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

plan-driven or agile: how good are the programming skills of the developers?

A

Agile methods need higher skill levels when compared to plan-driven

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

What are the main characteristics of agile development?

A
  • keep things small
  • deliver partially-completed software frequently
  • talk to the customer often
  • write more code than documentation
  • everyone on the team learns together
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are some agile practices?

A
  • short timeboxed iterations
  • continuous integration
  • daily unit testing
  • regular retrospectives
  • direct communication between devs and the cx
  • a single list of features and tasks
  • short-term estimation of dev tasks
  • information radiators
  • refactoring
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

There is ___ to do requirements in agile development

A

no standard way

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

Why is agile development important?

A
  • large feature sets could increase the cost for the customer
  • constant introduction of new technologies
  • new players enter the market
  • “small is beautiful”
  • if we listen to customer, we reduce our chances of being blindside by smaller, more flexible competitors
  • anything that helps reduce maintenance costs is awesome
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is agile all about?

A
  • keep process lightweight
  • making real progress in each iteration
  • communicating -> face-to-face when possible
  • actively gathering customer input
  • being willing to make minor changes to your process
17
Q

Scrum process cycle

A

Start with a product backlog that you loop through continuously grooming

Then you plan the sprints by looking through the backlog of tasks

Then you perform 2-4 week sprints and a daily scrum meeting

Once done all the sprints, you give the final product

18
Q

Can you add things to a sprint once it has started?

A

NO

19
Q

What is a product backlog?

A

Prioritized list of tasks that software development teams complete while creating new software or updating existing programs

20
Q

What is the scrum iteration process?

A

Software Product Development goes this way:
Step 1: Iteration planning - create a plan for one iteration
Step 2: Iteration Execution - implement the items in the plan
Step 3: Deliver the results of the iteration - give a demo

Repeat Steps 1-3 will be executed many times - based on release plan

Each cycle is a fixed-length timebox – note: you always end the iteration on schedule, even if it isn’t complete

21
Q

What are the scrum elements?

A

THREE Roles:
1. Product Owner
2. Scrum Master
3. Team Member

THREE Meetings:
1. Planning
2. Daily Scrum
3. Sprint Review

THREE Lists:
1. Product Backlog
2. Sprint Backlog
3. Impediments List

22
Q

Kanban focuses on ___

A

Maintaining a continuous task flow and continuous delivery, whilst not overloading the team with work that they cannot handle.

23
Q

Tell me about eXtreme Programming

A

Very fast no matter what, all about high velocity. Doesn’t care too much about quality, just want to launch with minimal errors. Iterative Development.

New versions can be built several times per day and increments are delivered to customers every 2 weeks.

All test must be run for every build and the build is only accepted if tests run successfully

24
Q

What is common between Scrum, XP, and Kanban

A
  • Visibility/Transparency
  • User Stories
  • Pull Based (work is pulled only if there is demand for it)
  • Definition is done
  • Sustainable Pace
  • Continuous Improvement
25
Q

Why might a product owner not be a good scrum master?

A
  • they may not be able to see deadlines
  • conflict of interest, may not see or listen to cx feedback
  • product owner is a full time job
26
Q

Tell me about kanban

A

Close to scrum, focuses on maintaining a continuous flow and delivery and is not given more work than it can handle, this is accomplished through the primary principle of kanban.

27
Q

Similarities between scrum and kanban

A

Pull System

Limit work in progress

Break Down Complex Tasks

High Value on Continual Improvement

28
Q

Give me the overview of each of Scrum, XP, and Kanban

A

Scrum
- Plan Sprint
- Work on items in sprint
- Review
- Retrospective

XP
- Plan release
- Plan iteration
- Work through items
- release when “done, done”
- Iterative retrospective
- release retrospective

Kanban
- Input queue
- Pull item to work
- Work until meets done criteria
- Repeat

29
Q

How do meetings work in Scrum, XP, and Kanban

A

Scrum
- Daily Standup
- Sprint Review
- Sprint Retrospective
- Sprint Planning
- Backlog Grooming

XP
- Release planning
- Iteration planning
- Standup
- Iteration Retrospective
- Release Retrospective

Kanban
- No Meetings

30
Q

How do the roles differ in Scrum, XP, and Kanban

A

Scrum
- Customer
- Product Owner
- Scrum Master
- Development Team

XP
- Customer
- Coach
- Team

Kanban
- Whatever you currently have lol

31
Q

How do artifacts differ in Scrum, XP, and Kanban

A

Scrum
- Card board
- Backlog
- Definition of Done
- Burndown

XP
- Board
- Charts
- MORE FUCKING CHARTS

Kanban
- Board
- Whatever the fuck kind of report you want to create

32
Q

What metrics are used in Scrum, XP, and Kanban

A

Scrum -> Velocity

XP -> Velocity

Kanban
- Lead Time
- Cycle Time
- Throughput performance
- due date completion

33
Q

What kinds of continuous improvements are used within Scrum, XP, and Kanban

A

Scrum
- Inspect & Adapt
- Sprint Retrospective

XP
- Iteration Retrospectives
- Release Retrospectives

Kanban
- Kaizen Culture
- Kaizen Blitz (wtf is kaizen)
- Slack
- continuous improvement - kaizen