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.
When you transition to agile and you have a reasonably size codebase, chances are quite good that you’ve been working on the product for a while. You certainly have legacy ways of thinking about the code and the tests. Now learn how to work yourself out of the technical debt you have accumulated.
Johanna Rothman writes on how she facilitated a project management clinic in which she overheard this statement: "We have a product owner who persists in changing the contents of the sprint during the sprint. This is difficult for us. It costs us to change the content." To Johanna, this is a huge pain and it is similar to multitasking.
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.