The scrum process provides for planning at different phases of a project to enable the delivery team and product owner, facilitated by the scrummaster to define product features with user stories and related definition(s) of ‘done’ for each sprint. With this in hand, the delivery team can achieve momentum to deliver working software with no interference.
There is no one solution to rolling out scrum in an organisation. This is understandable as each organisation has its own unique characteristics and challenges. As scrum seeks to complete a project over a series of sprints; organisations can borrow these principles to implement scrum over a series of iterations.
Win-win all round.

In my consultancy work with different organisations, I get asked what makes for an effective ICT strategy. Also on a related basis, is there a difference between and IS strategy and an IT strategy ? In this blog, I give my 2c on these two related topics. The ICT strategy must support both the organisation’s business strategy and also show how ICT can be used to provide opportunities for new ways of doing business. An effective ICT strategy is a combination of an IS strategy and IT strategy

In browsing some scrum related topics recently, I came across an interesting document by Michael James in which he lists characteristics and tasks that scrummasters can leave out in the day to day workings of a sprint. What I like about this checklist is it’s format, where the tasks and characteristics are grouped by interactions between the scrummaster and the product owner, the delivery team and the wider organisation. I have listed some of what I think are the more interesting points in the checklist.