Chapter 3 Flashcards
List
4 stages of a Scrum sprint
Plan
Build
Test
Review
List and Define
3 roles in Scrum
Product owner- creates and prioritizes backlog
Scrum Master- facilitates, removes obstacles, runs meetings, coaches
Team members
List and Define
3 artifacts of Scrum
Product backlog- prioritized list of product requirements or features
Sprint backlog- subset of above to be completed during sprint
Code Increment- result of a sprint
Define
Sprint Planning Meeting
Determine what items from product backlog can be delivered in time-box, move to sprint backlog. Decide team roles
Define
Daily Scrum Meeting
15 minutes
What did you accomplish?
What obstacles did you find?
What do you plan to accomplish before next meeting?
Define
What is Agility
Effective response to change
Effective communication among all stakeholders
Drawing customer into team
Rapid, incremental delivrey of software
Like making a meal and giving tastes along the way
List
Pros of Scrum
Product owner sets priorities
Team owns decision making
Documentation is lightweight
Supports frequent updating
List
Cons of Scrum
Difficult to control cost of changes
May not be suitable for large teams
Requires expert team members
List
Extreme Programming (XP) process
Planning
Design
Coding
Testing
Define
XP Planning
Begins with user stories, cost estimate (length of time), stories chosen for increment, delivery date set, project velocty estimated
Define
XP Design
KIS, encourages use of CRC cards
Define
XP Coding
Construct unit tests before coding, program in pairs
Define
XP Testing
Unit tests executed daily, acceptance tests defined by customer
List
Pros of XP
Emphasizes customer involvement
Establishes rational plans and schedules
High developer commitment to the projects
Reduced likelihood of project rejection
List
XP Cons
Temptation to ‘ship’ a prototype
Requires frequent meetingd about increasing costs
Allows for excessive changes
Depends on highly skilled team members
Describe
Kanban Framework
Visual presentation
Limits amount of work in progress at any time
Managing workflow to reduce waste
Making policies explicit, define ‘done’
Continuous improvement with feedback loops
Process changes made collaboratively
List
Pros of Kanban
Lower budget and time requirements
Allows early product delivery
Process policies written down
Continuous improvement
List
Cons of Kanban
Team collab skills determine success
Poor business analysis can doom
Flexibility can cause to lose focus
Development reluctant to use measurement
List and Define
DevOps
Continuous development in multiple sprints
Continuous testing with automatic tools used prior to integration
Continuous integration with new code added to existing
Continuous deployment
Continuous Monitoring of the production environment
List
Pros of DevOps
Reduced time to Deploy
Team has development and operations staff
Team has end-to-end ownership
Proactive monitoring
List
Cons of DevOps
Pressure to work on old and new code
Heavy reliance on auto tools to be affective
Deployment may affect the product environment
