I have been using SCRUM and XP principles/practices since early 2003 for various software projects.
Here is my take on how SCRUM/Agile software development has affected the typical roles in Software development for the Organizations adopting SCRUM/Agile.
Management, Leadership:
Requires management to delegate decision-making authority to the Scrum team, even allowing them to fail if necessary
SCRUM highlights the inefficiencies and critical constraints imposed all along the software delivery chain
No specialization in terms of skillset for the team members
Scrum requires constant monitoring both quantitatively and qualitatively
Lower Risks: At most you lose a Sprint’s work
Customers/Clients:
Real involvement – Sprint Demos/Reviews at the end of every Sprint
Faster and incremental deliveries
Requirements are barely sufficient – SCRUM provides a way to adapt and continually improve.
Product Owners:
Drive the overall vision of the product
Exclusively manage the Product backlog and stakeholders expectations
Sign-off on Sprint deliveries/results
Fully integrated in to and dedicated to the team
SCRUM Team/Developers:
Intensity: agile development is intense for developers
Team composition: Should consist of some senior developers
Must incorporate XP practices like Continuous Integration, TDD, Incremental Design, etc.
Co-Location for better communication/visibility
Technorati Tags: Agile, Agile Development Roles, Agile Management, SCRUM
About admin
I am Shashi Velur. I live in Austin, TX with my wife and daughter. I consider myself an experienced Enterprise Software Developer/Architect.
The views expressed are mine alone and do not necessarily represent the views of my current and any of my previous employers.
