In this first part of a two-part series, Mario Moreira writes that a reasonable application lifecycle management (ALM) product will have a common user interface for utilizing the ALM functionality. It will also include a meta-model and process engine to parse and share information across and amongst the various functions within the ALM framework. These technical needs must be accompanied by a strong business case for delivering higher customer value and new approaches for seamless integration.
In this second part of a two-part series, Mario Moreira explores the back-end disciplines of a lifecycle that establishes an ALM framework centering on customer value. If your organization has adopted agile and you are looking at building your ALM framework, consider an infrastructure and tooling that will help you establish and build customer value throughout the lifecycle.
In this article, the authors discuss how software configuration fits into products and projects, beyond managing and controlling source code and other developer assets. They look at the differences between internal and external products and where project fit into the equation.
For development, a production application should be fully baked and not in what would be considered a “development” state. Tracy Ragan explains that frequent releases are a basic requirement of rapid development methodologies like agile and this impacts the way in which development teams and production control teams must interact.
Think you know what your customer wants? Can you afford to be wrong? Based on the concept of tracer ammunition, which allows a shooter to follow the path of a bullet toward its target and adjust his aim as needed, tracer bullet software development can help you better understand your users’ wants so you can build a product that hits the mark.