Articles - Étudiants SUPINFO
The Agile Method is a particular approach to project management that
is utilized in software development. This method assists teams in
responding to the unpredictability of constructing software. It uses
incremental, iterative work sequences that are commonly known as sprints.
This is a simple definition of Agile, the complex definition of Agile is
for advanced users you can know more about the Agile process on complex
Scrum employs real-time decision-making processes based on actual
events and information. This requires well-trained and specialized teams
capable of self-management, communication and decision-making. The teams
in the organization work together while constantly focusing on their
common interests. To get more details on the complex definition of SCRUM
you can look at http://scrumreferencecard.com/
General Principles of the AGILE Method
Satisfy the client and continually develop software
Changing requirements are embraced for the client’s competitive
Concentrate on delivering working software frequently. Delivery
preference will be placed on the shortest possible time span.
Developers and business people must work together throughout the
Projects must be based on people who are motivated. Give them
the proper environment and the support that they need. They should be
trusted to get their jobs done.
Face-to-face communication is the best way to transfer
information to and from a team.
Working software is the primary measurement of progress.
Agile processes will promote development that is sustainable.
Sponsors, developers, and users should be able to maintain an
indefinite, constant pace.
Constant attention to technical excellence and good design will
Simplicity is considered to be the art of maximizing the work
that is not done, and it is essential.
Self-organized teams usually create the best designs.
At regular intervals, the team will reflect on how to become
more effective, and they will tune and adjust their behavior
The product vision is a definition of what your product is, how it
will support your company or organization’s strategy, and who will use
The product roadmap is a high-level view of the product
requirements, with a loose time frame for when you will develop those
requirements. Identifying product requirements and then prioritizing and
roughly estimating the effort for those requirements are a large part of
creating your product roadmap.
Stage 3: Realease Planning
The release plan identifies a high-level timetable for the release
of working software. An agile project will have many releases, with the
highest-priority features launching first. A typical release includes
The product owner, the master, and the development team plan
sprints, also called iterations, and start creating the product within
those sprints. Sprint planning sessions take place at the start of each
sprint, where the scrum team determines what requirements will be in the
During each sprint, the development team has daily meetings. In
the daily meeting, you spend no more than 15 minutes and discuss what
you completed yesterday, what you will work on today, and any roadblocks
The team holds a sprint review. In the sprint review, at the end
of every sprint, you demonstrate the working product created during the
sprint to the product stakeholders.
Stage 7: Sprint Retrospective
The team holds a sprint retrospective. The sprint retrospective is
a meeting where the team discusses how the sprint went and plans for
improvements in the next sprint. Like the sprint review, you have a
sprint retrospective at the end of every sprint.
AGILE project management roles
Development team: The group of
people who do the work of creating a product. Programmers, testers,
designers, writers, and anyone else who has a hands-on role in product
development is a member of the development team.
Product owner: The person
responsible for bridging the gap between the customer, business
stakeholders, and the development team. The product owner is an expert
on the product and the customer’s needs and priorities. The product
owner works with the development team daily to help clarify
requirements. The product owner is sometimes called a customer
Scrum master: The person
responsible for supporting the development team, clearing
organizational roadblocks, and keeping the agile process consistent. A
scrum master is sometimes called a project facilitator.
Stakeholders: Anyone with an
interest in the project. Stakeholders are not ultimately responsible
for the product, but they provide input and are affected by the
project’s outcome. The group of stakeholders is diverse and can
include people from different departments, or even different
Agile mentor: Someone who has
experience implementing agile projects and can share that experience
with a project team. The agile mentor can provide valuable feedback
and advice to new project teams and to project teams that want to
perform at a higher level.
AGILE project management artifacts
Product vision statement: An
elevator pitch, or a quick summary, to communicate how your product
supports the company’s or organization’s strategies. The vision
statement must articulate the goals for the product.
Product backlog: The full list
of what is in the scope for your project, ordered by priority. Once
you have your first requirement, you have a product backlog.
Product roadmap: The product
roadmap is a high-level view of the product requirements, with a loose
time frame for when you will develop those requirements.
Release plan: A high-level
timetable for the release of working software.
Sprint backlog: The goal, user
stories, and tasks associated with the current sprint.
Increment: The working product
functionality at the end of each sprint.
AGILE project management events
Project planning: The initial
planning for your project. Project planning includes creating a
product vision statement and a product roadmap, and can take place in
as little time as one day.
Release planning: Planning the
next set of product features to release and identifying an imminent
product launch date around which the team can mobilize. On agile
projects, you plan one release at a time.
Sprint: A short cycle of
development, in which the team creates potentially shippable product
functionality. Sprints, sometimes called iterations, typically last
between one and four weeks. Sprints can last as little as one day, but
should not be longer than four weeks. Sprints should remain the same
length throughout the entire projects.
Sprint planning: A meeting at
the beginning of each sprint where the scrum team commits to a sprint
goal. They also identify the requirements that support this goal and
will be part of the sprint, and the individual tasks it will take to
complete each requirement.
Daily scrum: A 15-minute
meeting held each day in a sprint, where development team members
state what they completed the day before, what they will complete on
the current day, and whether they have any roadblocks.
Sprint review: A meeting at the
end of each sprint, introduced by the product owner, where the
development team demonstrates the working product functionality it
completed during the sprint.
Sprint retrospective: A meeting
at the end of each sprint where the scrum team discusses what went
well, what could change, and how to make any changes.
If you need more informations about AGILE and SCRUM you can get more
complex informations with the next links: