Blog

    • 7 steps to efficient projects with SCRUM

    We have worked with SCRUM methodology for over ten years – but what does SCRUM mean in practice? Our project manager Mohammad Abou Samra will walk you through how we use SCRUM in our software development projects!

    1 Backlog grooming and pre-planning

    We plan our projects well – that makes us structured and efficient. The backlog contains all planned future issues. Before a new sprint, the product owner and SCRUM master goes through the backlog. Are issues sorted in the right order? Are they prioritized right?

    2 Sprint planning

    When planning a sprint, the SCRUM master, the product owner and the developers go through what should be done, estimate what resources each issue will require and decide the scope of the sprint.

    3 The scope is fixed

    Once the sprint has started, no changes can be done to the scope of the sprint. Only the product owner and the SCRUM master can change the scope. If the scope of the sprint needs to be clarified, the developers address the SCRUM master.

    4 Daily stand-up

    At the beginning of each day we hold a daily stand-up. This meeting should never take more than 15 minutes. We have a clear structure for the stand-up, which ensures that everyone makes themselves understood and to avoid misunderstandings. Everyone in the team answers three questions:

    • What have you done (yesterday)?
    • What will you do (today)?
    • Is there anything that blocks you from doing your issues?

     

    It’s the SCRUM master’s responsibility to resolves the blocks that are brought up during the meeting.

    5 Keeping an eye on DoD

    Our SCRUM masters keep an eye on DoD, Definition of Done, during the sprint. DoD is a checklist which specifies which demands and specifications an issue shall meet before it can be considered done. Each team member is responsible for checking DoD before they mark the issue as done. As an extra quality control, our SCRUM master goes through the DoD together with the developer before the developer releases an issue.

    6 Sprint demo

    At the end of a sprint, the SCRUM master demonstrates the work accomplished during the sprint to the product owner. All team members are present and all stakeholders at the client are welcome to join. The product owner and other stakeholders give feedback on the work.

    7 Retrospective

    When a sprint is completed we do an evaluation. We ask three questions:

    • What went well?
    • What can be improved?
    • What shall we improve in the next sprint?

     

    The SCRUM master takes responsibility for improvements to be made in the next sprint.

    SCRUM is an extensive framework which has existed for 25 years, and it’s often use in software development. For SCRUM to work well in practice, it’s important that the entire team works according to the same processes and principles. A tip is to create a how-to-guide describing the processes and interaction in your team – it makes it easier when new developers join the team.

    Mohammad Abou Samra, project manager and SCRUM master

  • Watch video of how it works here