Software Configuration Management Project Baselines A project baseline is the fundamental CM technique for release management. Configuration management has historically been about managing the acquisition of new products. To that end, a set of baselines is defined corresponding to various milestones in the product development cycle. These baselines reflect different expressions of the final product and include the functional, allocated, and released baselines. |
Austin Hastings
May 26, 2008 |
|
How Release Management Can Help Agile Teams As many have learned, using Agile methods can provide solid business benefits including earlier return on investment, earlier detection of failed efforts, and more satisfied stakeholders. However, when applying Agile methods to product-lines (and projects therein), often there are dependencies on other products (and their projects), services, and organizations that may run in a more waterfall or hierarchical manner. If the Agile project and product therein are self-sustaining with no dependencies on outside factors, life can be quite good. But most of the Agile projects I have worked with or visited have varying degrees of dependencies on other products or services that run in a more waterfall or hierarchical manner. |
||
The Practice of Good Release Management Processes in CM We build software as part of a system or as its own entire product. The goal is to meet the requirements established by the customer, the market and/or the cost/benefits analysis. Product releases are meant to move us from some starting point to our ultimate product over a period of time: months, years or even decades. Release management starts not with the delivery of software, but with the identification of what we're planning to put into the product. The timing and content of releases helps us to manage releases so that they are not too onerous on the customer and so that we stay in a competitive position with our products. Good release management processes will ensure that you know what is going to go into your product, what actually went into the product, and what changes the customer is going to realize upon upgrading. |
||
Release Engineering Best Practices G |
Anonymous
May 26, 2008 |
|
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!." |
||
![]() |
SCM Essentials for Small Teams Very small teams think that SCM (software configuration management) is not for them. Even the name sounds like a big thing: CM, configuration management. "Why should I care?" They |
Pablo Santos
May 26, 2008 |
Optimizing CruiseControl for Continuous Integration CruiseControl is a great tool for preventing against data loss and corruption. Michael Sayko explains in this article how this continuous integration tool can be implemented to assist development projects, even across the enterprise level. |
Michael Sayko
May 5, 2008 |
|
Make Clean: Usman's Law Usman's Law (named after a smart coworker of mine who spent months working with customer Makefiles). make clean is intended to take you back to a state where everything will be rebuilt from scratch. Often times it doesn't. Here's why. |
||
Transparency and Accountability Regular reporting increases transparency and accountability, which, while some developers may initially grimace at, the process eventually makes everyone's job easier. By accurately capturing and compiling this data, efficiency can be increased in more areas than you might have thought possible. |
||
Bringing Business Value to IT Governance For some organizations, IT governance is just another set of standards that is stated yet with few (or no) compliance expectations, little actual verification occurring, few or no metrics to indicate compliance, and even less use of the results by senior management to run their organization. Without support for standards, including practices, policy, verification, metrics and management’s commitment to use the results to manage the organization, IT governance, like any other standard, will only be perceived as yet another item that has little management support and is lacking value in the organization. |
Pages
Upcoming Events
Sep 22 |
STARWEST Software Testing Conference in Anaheim & Online |
Oct 13 |
Agile + DevOps USA The Conference for Agile and DevOps Professionals |
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |