Skip to main content

Scrum and Agile Project Management

These days it seems that everyone wants to be Agile.  This is a good thing as Agile presents a number of benefits to organisations that have a need for project based working.  There are however a number of misconceptions about what Agile is and how it works, one of the biggest is that Scrum is all that is required to manage projects in an agile way. (more…)

Definition of Done

Scrum requires that each Sprint deliver a usable product increment at the end of the time-boxed Sprint.  In order for the product increment to be usable it must have had all required work completed.   Any incomplete work is likely to render the product increment unusable, at least until the work has been completed in a later Sprint. (more…)

What’s a Story Point

When more than one team is involved in a project it becomes necessary to ensure synchronisation between the multiple teams. The Scrum of Scrums meeting is the process for ensuring this synchronisation. As with the Scrum meetings it is an opportunity to provide updates, discuss challenges faced and coordinate activities. (more…)

Scrum of Scrums

When more than one team is involved in a project it becomes necessary to ensure synchronisation between the multiple teams. The Scrum of Scrums meeting is the process for ensuring this synchronisation. As with the Scrum meetings it is an opportunity to provide updates, discuss challenges faced and coordinate activities. (more…)

MoSCoW Prioritisation

Prioritisation of requirements has always been important.  Even more so in Agile projects.  This is because in Agile time is fixed and it is scope that is more flexible.

The timebox nature of Agile methods such as Scrum and Atern mean that it is important that the whole team understands the priorities and has the same understanding of what the priorities mean.   Prioritisation is therefore vital to making progress on the right things and enabling the meeting of deadlines that results in successful delivery.

(more…)