release management


Defining Requirement Types: Traditional vs. Use Cases vs. User Stories

Charles Suscheck explains the differences among traditional requirements, use cases, and user stories by describing and providing an example of each.

Charles Suscheck's picture Charles Suscheck
A Framework for Agile

Bob Aiello discusses how CM and agile practices can go hand in hand - provided that you have a solid framework to work with. With agile's popularity seemingly always on the rise, alongside the need for CM, learn how having both benefits everyone onboard.

Bob Aiello's picture Bob Aiello
An Agile Approach to Release Management

For teams practicing Agile Software development, value working software over other artifacts, a feature from the release plan is not complete until you can demonstrate it to your customer, ideally in a shippable state. Agile teams strive to have a working system ("potentially shippable") ready at the end of each iteration. Release Management should be easy for an ideal agile team, as agile teams, in theory, are ready to release at regular intervals, and the release management aspect is the customer saying, "Ship it!."

Release Management - Making it Lean and Agile

Release Management is an awesome responsibility that plays a vital role in the success of a software development project. Releasing is often considered to be an activity that happens near the end of the process - a necessary evil perhaps, but no more.

Robert Cowham's picture Robert Cowham

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.