Release Management

Articles

Releasing SMURFS Instead of MVPs, Maybe We Should Be Releasing SMURFS

The term minimum viable product, or MVP, has come to be misunderstood and misused in many organizations. It doesn’t mean you should be releasing half-baked, barely feasible software. Instead, you should be thinking of your product’s capabilities as a Specifically Marketable, Useful, Releasable Feature Set—or SMURFS!

Matthew Barcomb's picture Matthew Barcomb
Project Management Framework Common Misconceptions about Agile: Agile Is Just a Project Management Framework

When it comes to transitioning to agile, if a team only goes off what it's heard from other teams and doesn't take a class or read any books about the process, misconceptions can abound. And that leads to problems. Read on to have three common agile myths debunked and to learn why agile is a cultural change, not just a project management framework.

Johanna Rothman's picture Johanna Rothman
Introducing the DevOps Database Gap Introducing the DevOps Database Gap

Yaniv Yehuda details how DevOps is a natural evolution within the software industry as it drives business value and enables the organization. This article will describe how database management and the database administrators need to be part of any comprehensive DevOps approach.

Yaniv  Yehuda's picture Yaniv Yehuda
Defining Requirement Types: Traditional vs. Use Cases vs. User Stories

If you have recently transitioned to an agile team, you may have questions about the differences between user stories and use cases, especially how they differ from tradition requirements writing. In this article, Charles Suscheck defines each of these requirements types and uses a running example to illustrate how they differ in a real-world setting.

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.