How I Scrum

I am writing this post to give a general view of how I have implemented the scrum to collaborate with my fellow professionals. To get the real knowledge about scrum & its history, I suggest you read the book. This will be my implementation which holds the essence of the scrum.

1.Backlog a.k.a To-do List

The Team gathers all the tasks that need to be done. I use Trello with multiple lists such as :

  • Backlog (to-dos)
  • Done
  • Review

You can use any other task management system where it allows you to create tasks & lists. If the team is located at a single physical place & meet there to work everyday, It is even possible to have a board with sticky notes on it.


The Sprint represents a duration of time between 1-2 weeks of concentrated work. Once the tasks for a sprint are chosen, they cannot be modified.

It is essential to keep Sprint periods short in order to quickly evaluate & improve the process.

3.Daily Stand-up

Every day the team meets at a fixed & previously agreed upon time for a duration of 10 to 15 minutes. Every member starts by describing :

  1. What they did prior to this Stand-up
  2. What are they going to do until the next Stand-up
  3. If there is any challenge or obstacle that is preventing or slowing them down with their task

If any team member faces an obstacle of any sort & another team member can help, they shall not make the meeting longer. They shall take note, wait till the Stand-up is finished & then have a separate meeting with that team member.

It is crucial to stick to points & not drag the meeting. The name “Stand-up” was chosen primarily to emphasize the necessity of the meeting to be short & concise.

If it takes more than 15 minutes, you are doing it wrong.

J.J. Sutherland the Founder of Scrum

4.Sprint Review

The last day of Sprint, The team gathers to present & review the work. This is also referred as “demo day”. The team should have something to present as a result of the works that has been done during the sprint.

Afterwards every team member providers their feedback regarding the process. This is not about blaming or complaining. The main topic of these feedbacks are :

  • What went bad during this sprint?
  • What could have gone better?

If there is any feedback of sort, the team should add it as a task to the backlog & then the next sprint cycle. It is important to figure out a way of testing or evaluating this improvement in the next sprint review.


With the information in hand & the backlog, the team plans the next sprint & the tasks to be done. It is crucial to start the next sprint as soon as possible in order to be more effective.