Release Management, the Super Discipline

[article]

By seeing the discipline’s tasks in context with other tasks while also understanding the attributes, dependencies and the connection between the tasks of various disciplines across the project, the lifecycle becomes clearer. Tasks in the early part of a project release include identify requirements, estimate requirements, prioritize requirements by release, and approve requirements. By having these tasks identified in a lifecycle model, those involved in the test discipline who are more commonly involved in the backend of the release lifecycle, can identify where their involvement (aka the role of test) in the requirements phase may be beneficial. In some of the requirements tasks, the test role can ensure that the requirements being identified are actually testable.

Within a release management approach, the disciplines can more clearly work together to focus on the release of deliverables or functionality from requirements to production. Since the focus of release management is on the release and the tasks that support the creation of the release, this approach allows a person or project team to see the overall picture and the placement of the specific task in support of the release.

Once the context and attributes are defined within a lifecycle model, there is clear identification of the technical and tracking components of release management. The technical component includes the technology and environments needed to support a release. For example, this would include design tools, development tools, SCM tool and repository, the test environments, etc. The tracking infrastructure includes the processes and output (aka, project release artifacts) needed to define and move the project that supports the release forward. For example, this would include the requirements for the release, a project plan, various procedures used during the release, roles and responsibilities on the project that is producing the release, etc.

About the author

Mario  Moreira's picture Mario Moreira

Mario Moreira is a Columnist for the CM Journal, a writer for the Agile Journal, an Author, an Agile and CM expert for CA, and has worked in the CM field since 1986 and in the Agile field since 1998. He has experience with numerous CM technologies and processes and has implemented CM on over 150 applications/products, which include establishing global SCM infrastructures. He is a certified ScrumMaster in the Agile arena having implemented Scrum and XP practices. He holds an MA in Mass Communication with an emphasis on communication technologies. Mario also brings years of Project Management, Software Quality Assurance, Requirement Management, facilitation, and team building skills and experience. Mario is the author of a new book entitled “Adapting Configuration Management for Agile Teams” (via Wiley Publishing). It provides an Agile Primer and a CM Primer, and how to adapt CM practices for Agile Teams. Mario is also the author of the CM book entitled, “Software Configuration Management Implementation Roadmap.” It includes step-by-step guidance for implementing SCM at the organization, application, and project level with numerous examples. Also consider visiting Mario’s blog on CM for Agile and Agile adoption at http://cmforagile.blogspot.com/.
 

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

May 04
May 04
May 04
Jun 01