Learn about simply implementing Agile Scrum using Trello and a Trello Scrum plugin. This method of planning work can tremendously increase your team's productivity.

1. Agile Framework and Scrum
Implementing the Agile Framework with Scrum and Trello

2. Business Platform Success
We design, build, and manage business
platforms by leveraging DataStax,
Sitecore, Salesforce, Quickbooks and
other cloud software.

3. Contents
● Purpose
● Basic Scrum Rules
● Scrum for Trello
● Burndown Chart
● Agile Alternatives
● Agile Scrum Certification

4. Purpose
The Scrum Guide™ defines it as follows:
Scrum (n): A framework within which people can address complex
adaptive problems, while productively and creatively delivering
products of the highest possible value.

5. Purpose
● Quick
● Easy (if the rules are followed…)
● Flexible
○ As project goals change, the Scrum process makes it easier to
adapt to these changes.

6. Basic Scrum Rules
● Use Scrum if…
○ The project scope is not clearly defined
○ Project requirements will likely change
○ Estimating/planning is difficult
○ Project is an iterative process
○ Success is defined by customer satisfaction
○ Incremental results have value

7. Basic Scrum Rules
A Scrum Team consists of the following:

8. Basic Scrum Rules
● Sprints: essentially = a agile “cycle”
○ After a sprint ends, another sprint begins
● Daily Scrums: usually ~15 min meetings to go over what has
been done yesterday, what will be done today, and what
blockers there are if any.

9. Basic Scrum Rules
Scrum Checklist
● Scrum Team - 1 Product Owner, 1 Scrum Master, and 3-9 members of
the Development Team
● Sprints with a time-box of one month or less
○ No changes are made that would endanger the Sprint Goal
○ Quality goals do not decrease
○ Scope may be clarified and re-negotiated between the Product Owner
and Development Team as more is learned
● Only the Product Owner can cancel a Sprint within the time-box

10. Basic Scrum Rules
Scrum Checklist
● 15-minute Daily Scrums
Sprint Reviews at the end of a Sprint
● Three-Hour Sprint Retrospectives for one-month Sprints
● Product Backlog
● Sprint Backlog
● Increment (all Product Backlogs) must be done by the end of a Sprint

11. Scrum for Trello
● Scrum for Trello, a Chrome, Firefox,
and Safari extension, is a tool to help
make the Agile process easier.
● Displays estimated vs consumed hours
on each Trello card.
● Each card represents a user story.
Example Board
https://trello.com/b/6otslC4i/template-
board-agile-with-trello

12. Scrum for Trello
• The default values are ?, 0, 0.5, and the Fibonacci numbers.
• However, the values can be changed:

13. Scrum for Trello

14. Scrum for Trello
● Trello treats lanes and the use of a Burndown Chart based on
certain keywords.
○ “No Burn”: Cards in a lane with this keyword will not contribute
its estimated / consumed hours into the final Burndown Chart.
○ “Done”: This lane no longer contributes its cards to the Burndown
Chart.

15. Burndown Chart
● Burndown Chart is a Trello plugin that integrates with Scrum for
Trello.
● Displays cards and hours completed.
● Ideal Burndown Line: represents the ideal daily trend if the
team is uniformly productive, ideally this is the rate at which we
strive to complete work at.
● Using the data from the cards, the plugin outputs an Estimated
Completion Date.

16. Burndown Chart
● Overtime, hours are added to
the previous sprint.
● The ideal Burndown Chart has
“hours completed” increasing
at the same rate “Ideal
Burndown” is decreasing.
● “Hours Remaining” is expected
to have a see-saw pattern, since
hours are reset with each
Sprint.

17. Burndown Chart
To change the range of dates the graph displays:

18. Burndown Chart
● Sharing / embedding a Burndown Chart requires a paid account
● Shared Boards allow users to view the information via an URL,
but not edit.
● Embedded Boards allow boards to be added to a webpage.
○ Must be a shared board.

19. Agile Alternatives
● Traditional Waterfall
○ Assumes all requirements
are finalized in the
beginning of the project
● Systems Development Life
Cycle
○ Each phase uses the results
of the previous phase

20. Agile Alternatives
● Kaban
○ Can be thought of as a “pipeline,” with feature requests coming through
one end and improved products/services coming out the other.
○ Limits the amount of work-in-progress tasks based on the phase with the
“weakest link”
■ Reveals bottlenecks so it can be addressed ahead of time.

21. Agile Scrum Certification
● To be certified as either a Professional Scrum Master (PSM) or
Certified Scrum Master (CSM):
○ Optional: Scrum.org Professional Scrum training class
○ Required: the respective Certification Assessment
Link: https://www.scrum.org/professional-scrum-certifications

22. Resources
● Scrum Certification: https://www.scrum.org/professional-scrum-
certifications
● Official Scrum Guide: http://www.scrumguides.org/scrum-
guide.html#events
● Scrum Master Training Manual:
https://mplaza.pm/downloads/Scrum%20Training%20Manual.pdf
● Scrum for Trello: http://scrumfortrello.com/
● Burndown for Trello: https://www.burndownfortrello.com/help.php
● Waterfall: http://www.umsl.edu/~hugheyd/is6840/waterfall.html
● SDLC: https://en.wikipedia.org/wiki/Systems_development_life_cycle
● Kaban: http://kanbanblog.com/explained/

23. Data & Analytics
Cassandra, DataStax, Kafka, Spark
Customer Experience
Sitecore
Information Systems
Salesforce, Quickbooks, and more
www.anant.us | solutions@anant.us | (855) 262-6826
3 Washington Circle, NW | Suite 301 | Washington, DC 20037