Scrum Operations Roles and Responsibilities
April 10, 2009 | Author: PM Hut | Filed under: SCRUM
Scrum Operations Roles and Responsibilities
By Aaron Sanders
Scrum Operations Role definition
- Keep products running in production
Scrum Operations Responsibilities
- Design hardware configurations for BCP, security, monitoring, availability during product design stage
- Responsible for getting the required hardware using the “HRC” process
- Set up staging, production environments (and in some cases the QA environment)
- Post production monitoring, and troubleshooting of product/services
- Owns OPS Health Status of releases/projects in SM dashboard
Aaron Sanders, always in the search for a better way to do business, has learned of Agile early in this decade, and incorporated its principles in his place of work. Recently, he was involved in pushing the definition of Agile to new levels at Yahoo! He is currently collaborating with organizations to steward the emergence of these Agile values and enable widespread adoption. Aaron Sanders writes extensively about Agile in his blog, constant change.
Related Articles
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
All fields marked with " * " are required.











1 person has left a comment
Important aspects I missed in the past when working with operations:
- Be ready to be involved early, take responsibility. THINK and ASK questions to understand your role in this specific project.
- Improve. Don’t stop if it is somehow working.
- Teach development actively and help them to improve. Don’t wait till dev team runs into trouble and don’t blame them (as they should not blame you). Offer help as soon as you see any problems.
- Talk to the product owner, try to understand what he is talking about. Your job is not about playing with servers and operating systems but to generate value by running a solution that is required to achieve the goal/vision of the company.
- Be friendly, think about hanging around for some beers with the guys from dev team.