SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
Get all the information you need
This is a critical point for a project’s success:
The basis for the whole project depend on it, as it is necessary to have the right tools
to work with.
Any and all information you can get can be valuable:
◦ Technical Proposal
Share all the information with your
team and listen to their opinions.
Get them involved and excited
about the project, so they feel it is
If changes are required, discuss it
with everyone involved and find the
right solution together.
Get the whole team involved in the process
The Master Plan
◦ Technical Details
Think about the big picture:
Having a global vision of the project, without forgetting the smaller details, will help you
get more clarity to define:
Plan the Sprint Meetings
One Rock at a Time
Divide the project into Rocks or Big Features,
and focus on one at a time.
These Rocks will then become epics.
All the cards in your board should belong to a
specific epic, with only a few exceptions.
Divide each “Rock” into pieces
Think of them as lego pieces that will help build
Make sure each piece is: Independent,
Estimable and Simple.
Each piece will become a story or card on your
board. (Trello / Jira / Pivotal).
Focus On Your Mission
Plan out what you wish to accomplish at the end of
the day, and stick to your main mission.
Constantly show progress to your client: Remember
that they are as in love with the project as you are,
and want to be part of building it.
If you don’t accomplish your mission at the end of
the day, you’ve wasted a day.
Only 60% of a sprint’s tasks are identified at the
Source: Agile Project Management Scrum (Schwaber 2004)
If a setback occurs that will
make it impossible to
complete the current sprint,
it should be placed in this
category and be regarded as
If a feature/task was not
identified during the
planning meeting, but is not
related to the current
sprint, it should be placed in
These features are out of
the product’s scope. No
matter how easy or exciting
they are, they most be
placed in this category.
New pieces can (and will) emerge
For each iteration, new requirements can (and will) emerge: It is our task to identify where
to place them:
Never say “No”
Manage client’s expectations.
Create a card, document it and send it to
Evaluate the effort required to complete
this new requirement and put it in writing.
We all want to be better at what we do
Make sure that every member of your team
is giving his/her best.
Take time to answer questions.
Congratulate them when things are getting
done, and push them when they could be
Challenge them: Everyone wants to learn
new things. All the time.