Slide Deck 2 Flashcards
What are the four Agile Manifesto things?
Individuals and Interactions OVER Processes and Tools
Working Software OVER Comprehensive Documentation
Customer Collaboration OVER Contract Negotiation
Responding To Change OVER Following A Plan
What is rapid software development?
most important requirement for software systems nowadays. Software has to evolve quickly.
What are the 12 principles of agile methods?
- Satisfy the customer
- Welcome change
- Deliver working software frequently
- Work Together
- Trust and Support
- Face-to-face communication is best
- Working software
- Promote sustainable development
- Continuous attention
- Maintain simplicity
- Self-organizing teams
- Reflect and Adjust —- Introspection - teams should regularly review itself and its processes to try and improve
What are some problems with agile methods?
- 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
What is plan-driven development?
Based around separate development stages with the outputs to be produced at each of these stages planned in advance.
plan-driven or agile: is it important to have a very detailed spec and design before moving to implementation?
Should user plan-driven approach
plan-driven or agile: Is an incremental delivery strategy, where you deliver the software to customers and get rapid feedback from them, realistic?
Should use agile methods
plan-driven or agile: How large is the system that is being developed?
Agile is good for small co-located team, for large teams, plan-driven is the way to go
plan-driven or agile: What type of system is being developed?
Plan-driven is possibly a must for systems that need a ton of analysis before implementation
plan-driven or agile: What technologies are available to support system development?
Agile methods rely on good tools to keep track of an evolving design
plan-driven or agile: how good are the programming skills of the developers?
Agile methods need higher skill levels when compared to plan-driven
What are the main characteristics of agile development?
- keep things small
- deliver partially-completed software frequently
- talk to the customer often
- write more code than documentation
- everyone on the team learns together
What are some agile practices?
- 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
There is ___ to do requirements in agile development
no standard way
Why is agile development important?
- 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
What is agile all about?
- 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
Scrum process cycle
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
Can you add things to a sprint once it has started?
NO
What is a product backlog?
Prioritized list of tasks that software development teams complete while creating new software or updating existing programs
What is the scrum iteration process?
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
What are the scrum elements?
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
Kanban focuses on ___
Maintaining a continuous task flow and continuous delivery, whilst not overloading the team with work that they cannot handle.
Tell me about eXtreme Programming
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
What is common between Scrum, XP, and Kanban
- Visibility/Transparency
- User Stories
- Pull Based (work is pulled only if there is demand for it)
- Definition is done
- Sustainable Pace
- Continuous Improvement
Why might a product owner not be a good scrum master?
- 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
Tell me about kanban
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.
Similarities between scrum and kanban
Pull System
Limit work in progress
Break Down Complex Tasks
High Value on Continual Improvement
Give me the overview of each of Scrum, XP, and Kanban
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
How do meetings work in Scrum, XP, and Kanban
Scrum
- Daily Standup
- Sprint Review
- Sprint Retrospective
- Sprint Planning
- Backlog Grooming
XP
- Release planning
- Iteration planning
- Standup
- Iteration Retrospective
- Release Retrospective
Kanban
- No Meetings
How do the roles differ in Scrum, XP, and Kanban
Scrum
- Customer
- Product Owner
- Scrum Master
- Development Team
XP
- Customer
- Coach
- Team
Kanban
- Whatever you currently have lol
How do artifacts differ in Scrum, XP, and Kanban
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
What metrics are used in Scrum, XP, and Kanban
Scrum -> Velocity
XP -> Velocity
Kanban
- Lead Time
- Cycle Time
- Throughput performance
- due date completion
What kinds of continuous improvements are used within Scrum, XP, and Kanban
Scrum
- Inspect & Adapt
- Sprint Retrospective
XP
- Iteration Retrospectives
- Release Retrospectives
Kanban
- Kaizen Culture
- Kaizen Blitz (wtf is kaizen)
- Slack
- continuous improvement - kaizen
