So you’ve started you’re Agile project and the first thing that a team member asks you is “What is my Role and what are my Responsibilities?” At this point it’s common for Agile practitioners to start waxing philosophically about shared responsibility, the advantages of being multi-skilled and how responsibility should be shared by the team.
Although this is all well and good, it’s not concrete advice and does not directly answer the question. From the point of view of a developer (or Analyst, or Tester etc) that is accustomed to working in a structured environment the lack of clearly defined roles and responsibilities can be very unsettling.
I’ve used variations of the following framework on previous projects. I’ve found it useful in that it does not explicitly define what an individual should do, but provides enough guidance to ensure that team members are comfortable.
Read the rest of this entry »
Filed under: Agile Software Development, Cultural Change, Organisation Change, Project Management, Scrum
When an Agile methodology is introduced to an organization for the very first time, it’s quite common for the client to ask: What are the characteristics that indicate a project will have the highest likelihood of success? Most experienced Agile practitioners have an intuitive feeling for which projects would be successful using an agile methodology. This includes such factors as the project having a direct contribution to business value, or having a dedicated business customer. Even though this may be understood by the experienced practitioner, that does directly help the program manager with the selection process.
This article describes an “Agile Scorecard” that can be used as a first pass filter for selecting Agile projects. The intention of the Agile Scorecard is to provide a simple manner in which projects can be reasonably selected by a project team that is unfamiliar with agile methods.
Read the rest of this entry »
Filed under: Agile Software Development, Planning, Project Management, Scrum
Recent Comments