Our Blog

So you’ve got your backlog in order, estimated your backlog, clarified your requirements, planned your sprint and created a collaborative workspace. You’ve sprinted to achieve your sprint goals, run daily stand-up meetings and tracked progress with a daily burndown chart. Now you’ve come to the end of your Sprint and finished when you said you would. All that’s left to

So you’ve got your backlog in order, estimated your backlog, clarified your requirements, planned your sprint and created a collaborative workspace. You’re sprinting to achieve your sprint goals, running daily stand-up meetings and you’re tracking progress with a daily burndown chart. Now you just need to finish when you said you would… What a great idea! What an insight! If

So you’ve got your backlog in order, estimated your backlog, clarified your requirements, planned your sprint and created a collaborative workspace. You’re sprinting to achieve your sprint goals and running daily stand-up meetings. Now you’re ready to track progress with a daily burndown chart… “Oh dear, it seemed to be going so well” Often in traditional development projects, everything seems

So you’ve got your backlog in order, estimated your backlog, clarified your requirements, planned your sprint and created a collaborative workspace. You’re sprinting to achieve your sprint goals; now you’re ready for Step #7 – Stand up and be counted! Hold a daily stand-up meeting. The whole team must be present. It’s not optional. The whole team must be involved.

So you’ve got your backlog in order, estimated your backlog, clarified your requirements, planned your sprint and created a collaborative workspace. Now you’re ready for Step #6 – Sprint! Scrum does not really prescribe how you should go about delivering the tasks in your Sprint. Scrum is an agile management practice and doesn’t really cover agile engineering. XP (Extreme Programming)

Once you’ve completed Step #3 and clarified the requirements for all the Product Backlog items targeted for your Sprint, the next step is to plan the Sprint in detail… Sprint Planning Workshop (Part 2) The first part of the Sprint Planning Workshop (in the last step of this series) was focused on clarifying the requirements for the selected Product Backlog.

If you’ve followed the first 2 steps in the ‘How to Implement Scrum in 10 Easy Steps’ series, you should now have your product backlog in order and have estimated its size using Fibonacci points. The next step to implement Scrum – Step #3 – is Sprint Requirements. Sprint Requirements Workshop Call a Sprint Requirements meeting. Make sure the meeting

In step 1 – the first article of my ‘How To Implement Scrum in 10 Easy Steps’ series – I described ‘how to get your backlog in order‘. If you’ve completed step 1, congratulations! Because it’s the biggest step. And the foundation for all else that follows. Whether or not you implement Scrum. If you haven’t completed step 1, you

So you want to implement Scrum? And you like the idea of making it easy? Then listen up. This is step 1 in my series: How to implement Scrum in 10 easy steps. This is not only the 1st step. It’s the most important step. Unless you can take this step, go no further. Do not skip it. I promise