Agile Terms Flashcards
Four Manifesto Values
1) Individuals and Interactions over Processes and Tools
2) Working Software over Comprehensive Documentation
3) Customer Collaboration over Contract Negotiation
4) Responding to Change over Following a Plan
Agile Principles: Customer
1) Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2) Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
3) Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4) Business people and developers must work together daily throughout the project.
Agile Principles: Team
1) Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
2) Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
3) Working software is the primary measure of progress.
4) The most efficient and effective method of conveying information to and within a development team is a face-to-face conversation.
Agile Principles: Product and Process
1) Continuous attention to technical excellence and good design enhances agility.
2) Simplicity-the art of maximizing the amount of work not done is essential.
3) The best architectures, requirements, and designs emerge from self-organizing teams.
4) At regular intervals, the team reflects on how to become more effective, then tunes and adjusts accordingly.
Three Pillars of Scrum
Transparency, Inspection, Adaptation.
Transparency
The process is visible so the work and the definition of done are agreed upon.
Inspection
Timely checks on work to assess progress toward the goal.
Adaptation
Adjustments are made to processes when work is not getting done.
Four Scrum Events
Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective.
Caves and Commons
Providing both a colocated area for teams to work and separate quiet space for individuals when they need to focus on something without distraction.
Sprint Planning Meeting Inputs
1) Ordered product backlog
2) Record of completed items
3) Knowledge of past performance
4) Development team capacity
Daily Scrum: Scrum Guide
1) Team member attended and facilitated
2) No attendance by Scrum Master
3) No participation from PO
Daily Scrum: Scrum Alliance
1) Entire Scrum team attends
2) Any Scrum team member can provide updates
3) Any interested party can attend provided they do not contribute.
Backlog Refinement
1) Ongoing process used by the PO to get more information about product needs and requirements.
2) Scrum meeting after the midpoint in the sprint. During this meeting the PO presents candidates for the next sprint and the development team evaluates the candidates.
Item Ready For A Sprint
1) Proper size can be completed in a sprint
2) Dependencies identified both upstream and downstream
3) Story has been sized by the development team
4) Acceptance criteria have been defined
