Is Scrum Evil?

scrum1SCRUM was designed with a particular purpose in mind, and it has suffered with too close an association with Agile (which is broader methodology).

At best, SCRUM is a sub-Agile method, which assumes all project memebers are dedicated, and in same location.  The Product Owner is CRITCAL component on a SCRUM project.  And this is where SCRUm can go awry – if the project has a Product Owner who is not sufficiently enaged with the project, or lacks skills to make good judgement calls on user stories.

Scrum is an Agile development framework that Jeff Sutherland invented at Easel Corporation in 1993. Jeff worked with Ken Schwaber to formalize Scrum at OOPSLA’95. Together, they extended and enhanced Scrum at many software companies and helped write the Agile Manifesto.

“Is Scrum Evil?” Beyond our session at XP Day Paris « Eric Lefevre-Ardant on Java & Agile

World Usability Day

worldHuman Factors International are running an essay competition, with a hard topic – How can the User Experience Community support the future of sustainability? My definition of User Experience may vary from others, as there are a lot of differing opinions as to aims and scope.  This highlights the importance of the user experience, and as everyone sees the world a little differently to each other.  But I believe in keeping things simple – User Experience incoroporates the design and functionality heuristics of a website.  Pandering to users can be a disaster, so it is a fine line between Good/Bad User Experience.   The “customer is always right” can be disasterous in software development.  Just because someone knows what they want, it doesnt mean it is what they need, or indeed if they actually want it!  How it can affect sustainability is a very (deliberate, I’m sure) open question.

World Usability Day


Scrum also developed in the 80’s and 90’s primarily with OO development circles as a highly iterative development methodology.

Scrum concentrates on the management aspects of software development, dividing development into thirty day iterations (called ‘sprints’) and applying closer monitoring and control with daily scrum meetings. It places much less emphasis on engineering practices and many people combine its project management approach with extreme programming’s engineering practices. (XP’s management practices aren’t really very different.)