 |
|||||
|
|||||
 |
|
|
|
||
 |
 |
 |
 |
 |
 |
|
|
|||||||||
|
05 |
What We Think |
||||||||||||||
 |
||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Are Project Managers Not Needed With Scrum?
In my last two entries I wrote about managers being excluded from Scrum and why Scrum Masters are no Project Managers. Does this mean that management is not needed? Are all management positions obsolete in software development with Scrum? Certainly not. The reason why managers often get bashed when talking about software development with Scrum, is because of the scope of Scrum. Scrum focuses on project execution, from project inception to project completion. This is on a level that an empowered team can handle. No managers needed.
Are Scrum Masters The New Project Managers?
Yesterday I registered for a website, and the drop down list for job titles had entries for ‘Project Manager/Scrum Master’ and ‘Developer/Engineer’. I was in a bit of a dilemma there. I am currently Scrum Master AND developer on my team. I never really considered Scrum Master being a job title, so I picked developer. Problem solved, right? But wait, ‘Project Manager/Scrum Master’?! Are they the same? Same category at least? Is a Scrum Master a lightweight Project Manager? – I think: No, possibly and sort of.
Last week I gave a short introductory presentation about Scrum at our company meeting. I explained how the team picks the highest priority user stories from the Product Backlog, and turns them into a potentially shippable product increment during a sprint. The question arose as to who would tell the team how to do this? The answer was quite simple, “No one does“. I briefly described how Scrum cherishes empowered teams. The team members will figure it out themselves, assuming, of course, the team has all of the required skills to achieve the task. The person who asked the question didn’t seem to be convinced. Obviously, I didn’t do a very good job of explaining it. I’ll try again with the following metaphor (I wish I had figured this out before the presentation).
As an IT professional have you ever been asked by a client to develop something that has no apparent business benefit? Did you do it? Did you ask the question, where is the benefit in doing this? Did you even realise that this had no business benefit? Well, chances are we’ve all been involved in projects which have questionable benefits, at best, for the business.
The Four, No FIVE Tensions of Software Development
Most people that do software development understand the idea of “tension” and what it means to projects. Most customers also understand this as well. Most people recognise four “tensions” when it comes to software development projects:
|
 |
categories archives
back to what we think |
|||||||||||||||||
 |
|||||||||||||||||||
|
 |
|
|||||||||||||||||
 |
 |
 |
|||||||||||||||||
 |
home | what we do | why choose us | who we are | what we think | contact us |
 |
|||||||||||||||||
 |
...follow us on twitter |
 |
|||||||||||||||||
 |
|||||||||||||||||||
 |
|||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
© 2009 Integration Works Limited |
||
|
|
|