Four Values of Agile Common Agile methodologies Scrum

Scrum 3 pillars - Transparency -> Inspection -> Adaptation

Extreme Programming (XP)
Individuals and interactions over processes and tools. Kanban
Lean product development
Customer collaboration over contract negotiation. Feature-driven development
Dynamic Systems Development Method (DSDM)
Working software over comprehensive documentation. Crystal Family of methods
5 fundamental values - focus, courage, openness, commitment and
respect
Sprints - time limited mini project in which the team releases a
potentially releasable product with a duration of 1 month or less.

Responding to change over following a plan. Scrum Team Roles:

Development Team - self organizing, cross functional team who

12 Principles of Agile Manifesto
Satisfy customer through early and continuous delivery of working software.
Welcome changes even in a later stage of development for the customer's competitive advantage.
Deliver working software frequently with a preference to shorter timescale.
Business and development team must work together daily throughout the project.
Motivate individuals by giving them the environment and support they need and trust them.
Face to face conversation is more effective and efficient to and within the development team.
Working software is the primary measure of progress.
Sustainable development - sponsors, developers and users must maintain a constant pace.
Technical excellence and good design enhances agility.
Simplicity - maximize the amount of work not done - do only what the customer need.
Self-organizing teams - provides best architecture, requirements and design.
Reflect and adjust at regular intervals to become more effective.
build the product increments during each sprint.
Product Owner - manages and prioritizes back log with the
assistance of scrum master and developers, make sure all have a
shared understanding of the project goals.
Scrum Master - Servant leader to the development team, meeting
facilitator, team coaching, helps the organization to adopt scrum
practices.
Scrum Activities:
Product backlog refinement - The team discusses and updates the
items in backlog.
Sprint Planning Meeting -> Daily Scrum -> Sprint review -> Sprint
retrospectives -------- Inspection and adaptation (2 pillars).

Sprint planning meeting - defines the sprint goal based on the

estimates from dev team, product owner presents the updated
backlog.

Daily Scrum - scrum master facilitates this meeting primarily for the
dev team to sync their work and report any issues.

Scrum of scrums - multiple Serum teams might need to coordinate

their work (Scrum of scrums of scrums)

Sprint Review - includes development team, the product owner, and

the Scrum Master (and potentially other stakeholders). The team
demos the increment work to the product owner, decides whether it
is done.

Sprint Retrospective - primarily for development team to do their

final "inspect and adapt". Timing is after sprint review but before
next sprint planning.

Scrum Artifacts:

Product Increment - which the dev team builds during a sprint that
the team and the product owner needs to define what is "done" and
share this understanding.

Product backlog - single source of all work - prioritized list (by

product owner) of all work that includes features, functions,
requirements, quality attributes, non-functional requirements,
enhancements and fixes. This process is called as backlog
refinement" or "grooming the backlog" - done be dev team and
product owner.

Sprint backlog - highly visible view of the work being undertaken,

only be updated by dev team, subset of product backlog, the team
develops a plan on how to achieve it.

Agile Page 1