Tagged with Agile

The ‘Dark Side’ of Scrum

A collegue of mine made me aware of a nice post from Daniel Markham, who’s written on Agile ruined his life“. In most of the post he describes his opinion of agile consultants who try to teach agile and software development best practises without having any clue about the work of a software developer.

But if you’re going to train something, you should be able to do it. And I mean do it to a very high level of expertise. An agile coach should be able to code, perform analysis, manage the project, test — anything that needs doing on a project. If she can’t, then how can you talk to her about your particular situation?

Nice article to read, if you do Agile/Scrum or plan to introduce it to your company. Not that I agree with everything Daniel is writing but there is some (not so) hidden truth in some of his words and phrases.

-> Daniel Markham: Agile ruined my life

Tagged , ,

Scrum & Agile Development

Scrum is an iterative incremental framework for managing complex work (such as new product development) commonly used with agile software development.

Although Scrum was intended for management of software development projects, it can be used to run software maintenance teams, or as a general project/program management approach.

Scrum is a “process skeleton,” which contains sets of practices and predefined roles. The main roles in Scrum are:

  1. the “ScrumMaster”, who maintains the processes (typically in lieu of a project manager);
  2. the “Product Owner”, who represents the stakeholders;
  3. the “Team”, a cross-functional group of about 7 people who do the actual analysis, design, implementation, testing, etc.

Here is my collection of Scrum resources in the world wide web:

Here are some articles I find very interesting:

Next week I will attend the Certified ScrumMaster training in Munich, done by Boris Gloger. So more posts about Scrum are about the follow this one.

Tagged , , , , , ,