Agile Manifesto Flashcards
Principles behind the Agile Manifesto 1.
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
Principles behind the Agile Manifesto 2.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
Principles behind the Agile Manifesto 3.
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Principles behind the Agile Manifesto 4.
- Business people and developers must work together daily throughout the project.
Principles behind the Agile Manifesto 5.
- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
Principles behind the Agile Manifesto 6.
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Principles behind the Agile Manifesto 7.
- Working software is the primary measure of progress.
Principles behind the Agile Manifesto 8.
- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Principles behind the Agile Manifesto 9.
- Continuous attention to technical excellence and good design enhances agility.
Principles behind the Agile Manifesto 10.
10 .Simplicity–the art of maximizing the amount of work not done–is essential.
Principles behind the Agile Manifesto 11.
- The best architectures, requirements, and designs emerge from self-organizing teams.
Principles behind the Agile Manifesto 12.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
SCRUM pillar 1
Trasparency: This pillar involves giving visability to those responsible for the outcome
SCRUM pillar 2
Inspection: This pillar involves timely checks on how well a project is processing towards its goals, looking for problematic deviation or differences from the goals
SCRUM pillar 3
Adaptation: This pillar involves adjusting a process to minimize further issues if an ispection shows a problem or undesirable tred.
Development Team
who build the product increments in each iteration (sprint). The Development Team manages own work, are sel-organized and cross-functional
Produc Owner
is responsible for mixmizing the value of the product. This person has the sole responsability for managing the product backlogs (prioritization. accurancy, shared understanding, value and visibility)
SCRUM Master
is the responsible for ensuring that SCRUM is understood and used. He’s the servant leader to the development team, removing impediments to progress, facilitating events as needed. and providing coaching. ScrumMaster assists the product owner with managing the backlog and comunicating the vison, goal, and backlog item to development team.
Sprints
A sprint is a timeboxed (time-limited) to build a potentially releasable product (like a mini-project). Each sprint includes a sprint planning meeting, daily scrumb, the development work a sprint review mwwting and review retrospective.
Spring Planning Meeting
is used to determine what will be delivered in that sprint and how the work will be achived. The produc owner presents the backlog itmes and the whole team discusses them to create a shared understanding. Here the development team willl define what will be delivered on in the next sprit goal
Daily SCRUM
is the 15 minutes timeboxed daily meeting. Here the development team synchronizing activites, communicates, and raises issues. it is held the same place and time.
- What has been achieved since the last meeting?
- What will be done before the next meeting?
- What obstacle are in the way?
ScrumMaster makes sure these meetings happen and helps obstacles
Sprint Review
is a meeting held at the end of the sprint to iinspect the increment, or evolving product (backlog can change). The development team demonstrates the work that is done
Sprint Retrospective
team reflect o the process and look for opportunities for improvments (team incorporate the product owner’s feedbacks)
Product Backlog
is the ordered list of everithing that might be needed for the product. It serves as the single source for requirements. Backlog is dynamic and evolves as the product. it contains all requirements. Grooming is the process of adding more detail and order to the backlog and refining the estimates of the blacklog item.(grooming is done by development team and product owner)
