A training presentation I did for my previous team on how to manage projects the Agile way and also how to use Trello as a scrum board to manage their projects the agile way to achieve more in less time and be more productive.

1. AGILE
Project & Team Management

2. 18 Months
PROFESSIONAL EXPERIENCE
and still learning…
WHY CAN I TALK TO YOU ABOUT THIS?

3. EXPECTATIONS
qThis not about learning a new tool, but learning a
new philosophy & methodology.
qWhat you are about to learnmight be new and
intimidating. But just keep calmand take notes.
qI might be fast due to time, but this presentation
is quite comprehensive.
qBe Open-mindedand connectto my soul ;)

4. Did you know that at least 1 new
feature is being deployed on
Facebook every week?

5. Do you know what can help you
achieve your travel bucket list, get
the next job, write a book, prioritize
better or even plan & implement
half-time faster?

6. A whiteboard and a pad of
sticky notes
Well, and the knowledge of how to use
them, of course ;)

7. Its called “Agile”.
But here it’s something more
advanced, simple and a bit
intimidating.

8. AGILE
&
SCRUM

9. Agile refers to a set of “methods and
practices based on the values and principles
expressed in the Agile Manifesto”. which
includes things like collaboration, self-
organization, and cross-functionality of
teams.

10. Scrum is a framework that is used to
implement Agile development. Other framework
of Agile includes Kanban, Lean, Extreme developmentetc…
Scrum is:
o Lightweight (i.e. few rules)
o Simple to understand
o Difficult to master

11. A good analogy would be the difference between a recipe and a
diet. A vegetarian diet is a set of methods and practices based on
principles and values. A recipe for simple green salad would be a
frameworkyou can use to implement your vegetariandiet.
This is similar to the relationship between Agile
(the diet) and Scrum (the recipe you follow).

12. FIRST, LET’S UNDERSTAND THE
ROLES, TERMS & EVENTS USED IN
SCRUM !

13. qProduct Owner: The Product Owner should be a person with vision,
authority, and availability. The Product Owner is responsible for
continuously communicating the vision and priorities to the
development team. This person does not micro-manage as it is a self-
organised team.
qScrum Master: The Scrum Master acts as a facilitator for the Product
Owner and the team. The Scrum Master does not manage the team. The
Scrum Master works to remove any impediments that are obstructing
the team from achieving its sprint goals. Sometimes, the Product Owner
can also act as the scrum master in a small organisation.
qTeam: According to Scrum’s founder, “the team is utterly self
managing.” The development team is responsible for self organising to
complete work. Also, the team is always consisted of individuals (3-9
people) of different skill set.

14. q Sprint: This is the heart of scrum. A time period (typically 1–4 weeks) in
which development/creation occurs on a set of Project Backlog Items
that the team has committedto.
q Tasks: Work items added to the Sprint Backlog in Sprint Planning, or
during the Sprint, with an estimate of hours to complete within a short
period.
q Planning: At the beginning of a Sprint, the Scrum Team holds a Sprint
Planning event to Communicate the scope of work that is intended to be
done during that Sprint, Select & Prepare Project Backlog Items that can
be completed in one Sprint.
q Stand-Ups: It is a 15-minute time-boxed meeting for the Team to
synchronize activities and create a plan for the next 24 hours.
q Sprint Review & Retrospective: Review is held at the end of the Sprint to
inspect the results and adapt the Product Backlog if needed. The Sprint
Retrospective is an opportunity for the Scrum Team to inspect itself and
create a plan for improvementsto be enacted during the next Sprint.

15. Starting a Basic Scrum
Framework
HOW TO GET STARTED ;)

16. 1. Pick yourroles: You need a Product Owner, a Scrum Master, and team
members. Remember, there’s no room for egos in Scrum. Scrum runs on a
“servantleader” model.
2. Create yourproductBacklog: TheBacklogis where you listout everythingthe
project needs, ordered by importance. Keep in mind that the Backlogis never
complete. As the project takes shapeand new needs emerge, you will add to this.
The ProductOwner takes primarily responsiblefor this.
3. Plan yourSprint: Next, it’s timeto pick tasks from the backlogto be completed
in your Sprint.
4. Get to work: Timeto startworking on that Sprint! Team members work on their
tasks, and everybody checks in on their progress at the Daily/Weekly Stand-Ups.
This meeting lasts no more than 15-minutes and answers threequestions: What
did you work on yesterday? What will you work on today? Is there anything
blocking yourwork today that you need help with?
5. Reviewyourwork and Retrospecton yourprocess.
6. Repeat: With your first Sprint complete, it’s time to startover again. Pick more
tasks from the Backlogand repeat the process.

17. Making it Visual!
you need a scrum board.

18. My TrelloScrum Board isbroken up intoseven lists.
§ Resources: In thislist, I keepall tasks that are recurring. That wayI don’t have to
make anew cardeverytime I need to start anew idea creation. Just move that card
out from the Resourceslist.
§ Backlog: Here’swhere I keep my Backlog of tasks tobe worked on. When JJ tellsme
he has something he needs helpwith, I add it tomy Backlog list.
§ To Do: When I plan mySprint, I pull tasks from the Backlog tothis list. Thisisthe
current Sprint I’m working on.
§ Doing: When a task has been started, it getsmoved here.
§ QC: Quality check. As tasks are completed, theyget moved to “QC.”At the end of
the week, I review thislist tomake sure everything isup tosnuff.
§ Done: Passed quality check, ready tobe shipped! No more editsor reviews
necessary, it’sscheduledand readyfor action.
§ Blocked: Whensomething ispreventing me from completing atask or while working
on the task it occurrednoto make sense anymore. I move it to “Blocked”, along witha
comment about what the blocker is/Why.

19. Backlog
To Do
Doing
Ready for
QC
QC
Done
PO assigns tasks to
various team
members and move it
to To Do stage.
Move task to DOING
when member starts
workingon it
Tasks are created in
the Backlog.
Move task to READY
FOR QC once
development is done.
Member responsible
for Quality Check
moves task to QC
stage.
If the product doesn’t
pass the QC, then it
goes back to the Doing
stage.
Responsibility of PO
Responsibility of Team Member
Responsibility of Quality
Checker/ScrumMaster

20. NOW, LET’S GO SEE THIS IN
ACTION ON
We will do this in more detail at MCM on Feb 7th. Meanwhile you can go to
trello.com to explore it !

21. Different people understand Agile differently. Project managers
might see it as a new methodology of working, Managers might see
it as something that can improve business results because it worked
for other similar companies. Developers might see it as yet another
management idea.
To me, agile is more than that. It’s a new philosophy of work that
combines three things: feeling good, being disciplined and focusing
on results.
When in an agile team, I
o feel good because I work with great people, I have a
goal and I am very connected to results
o am disciplined because I know it helps the team and
because the team helps me
o focus on results because I know the team’s goal and it
satisfies me to fulfillit.

22. QUESTIONS?

23. THANKS !
Preparedby,
Josephus AYOOLA
MCVP B2C, AIESEC inBelgium 16.17