After researching Prince2 for nearly two and half years i’ve finally took a very deep breathe and signed up for two formal training courses on the subject. I’ve long been trying to identify the ‘correct’ way to manage web projects, but so far it has eluded me. I am hoping that Prince2 will help standardise the way I manage projects and make good use of the twelve years web experience I have to date.
Over the last couple of months I’ve also been integrating fundamental aspects of the SCRUM software development methodology at Magnum Photos where I hold the position of Group Web Director.
SCRUM and Prince2 could prove to be a killer combination, but they could also cause too much conflict. Prince2 is structured and process driven, whereas SCRUM uses the emperical approach to management.
{ 1 comment… read it below or add one }
Prince2’s Scoping, requirements, stages, boundaries, Changes control are indeed useful elements to plan and control websites projects.
But it’ a very formal approach that don’t reflect the reality of the web industry : anarchy
How to manage a web project :
Writing a unique document including a site map, wireframes and functional specifications
Managing your scrum team.
Breath, smile and try not to explode