Define the basics of Agile
-
-
Four values:
Most Important
Individuals and interactions
Working software
Customer collaboration
Responding to change
Agile Manifesto – 12 Principles (http://agilemanifesto.org/)
o
o
o
o
o
o
o
o
o
o
o
o
-
-
Important but not the focus
over processes and tools
over comprehensive documentation
over contract negotiation
Over following a plan
Our highest priority is to satisfy the customer through early and continuous delivery of
valuable ______
Welcome changing requirements, even late in development. Agile processes harness
change for the customer’s competitive advantage.
Deliver working ______ frequently, from a couple of weeks to a couple of months, with
a preference to the shorter timescale.
Business people and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support
they need and trust them to get the job done.
The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.
Working ______ is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers, and users
should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity – the art of maximizing the amount of work not done- is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and
adjusts its behavior accordingly.
Three Pillars of Scum
o Transparency
o Inspection
o Adaption
Characteristics:
Collaborative, relationship-based
Life cycles are Agile, iterative, and incremental
Scope is defined before each iteration
Adaptive life cycles are referred to as Agile life cycles
Agile is an umbrella term for over 80 methodologies
o Scrum, Kanban, XP, Lean, SAFe, Da
Agile is executed through Iterations:
o Product backlogs – prioritizes the list of all requirements/user stories
 User story – a specific way from the user’s point of view what it is they want and
why they want it
o
o
o
o
o
o
Agile teams – Self-managed/organized/directed
Development Team:
 Diverse, cross-functional representation of the individuals with the expertise to
build a product
 Typically, five to nine people
 N(N-1)/2 = lines of communication
Product Owner
 Represents the business
 Responsible for product ROI
 Decides on features and functionality
 Represents the scrum team to the business
 Responsible for the creation of the product backlog
 Ensures the most valuable work gets done first
Scrum Master
 Ensures the Scrum values, principles, and practices are embraced
 Functions as a coach and a facilitator
 Acts as a servant leader
 Helps organization adapt to Scrum approach
Sprint backlogs – sprint/iteration requirements
Timeboxed – events
 Sprints/iterations – 30 days or less
 Daily Standups – 15 minutes
Responsibilities of the team