Five Imperatives for Application Lifecycle Management


shares linked data. Use lifecycle queries to answer more meaningful questions such as “Which requirements are affected by defects?”  Hovering a mouse over link provides information about the artifact at the other end of the link.

Manually collect status reports

Collaboration is also about knowing what is going on without having to ask, team activites/events and changes are easily accessible and visible to every one


Dashboards and lifecycle queries provide real-time status of the team’s progress. Mini, personal dashboards are always accessible through out the user interface.

Rely on email discussions. Important discussions are lost to email and chat archives--project records are missing the “real reason” for decisions

All discussions in work items integrated on the plan.

ALM environment becomes an essential “archeological tool” for understanding the past, speeding later enhancements

Lengthy “on-ramp” for new team members

New team members can easily understand the context of activities

The image below shows a dashboard mashup with widgets containing information from Rational Team Concert , Requirements Composer , and Quality Manager . The information in the dashboard provides up to date status about the project.


10.  Mashup dashboards provide transparency across the team

The image below shows a “mini dashboard” that is always accessible from the side of the UI and is dockable on left or right. It serves as a portable mini personal dashboard that goes with a user wherever they go within the ALM solution, and can be shown or hidden at any time.


11.  A mini dashboard is accessible through out the user interface

The image below shows a mini dashboard for a user in Rational Team Concert . On this mini dashboard is a widget displaying changes to requirements in Requirements Composer . This is a mini dashboard mash up. Hovering the mouse over the link to the requirement causes a rich hover to appear with information about the status of a requirement in Requirements Composer. Users in need of instant information gratification will quickly become addicted to using mini dashboards!  17

A rich hover on link from the Mini Dashboard

Continuous Process Improvement

Process is more than a documented set of procedures. We design processes based on best practices gleaned from industry experience as a means to improving a team’s behavior and to help them succeed. Most behavior is habitual. When you define or change a process, you are asking an entire team of people to change their habits and adopt behaviors that at first may be difficult to understand. It can be quite hard to change one habit in one person. Yet, process changes frequently require new ways of thinking and new modes of behavior for a multitude of people. A well-designed ALM solution allows you to change that process as you learn and improve the team dynamic.



Ignore process altogether or treat it like an unnecessary burden.

Realize that a well-defined process can help your team establish a rhythm and reduce unexpected problems from rogue behavior.

Define process improvements goals without making results of process improvement visible


Use dashboards to make area of improvements visible across the teams. For example, if you are struggling to burn down across an iteration, make the iteration burndown across the teams visible an dashboard, and watch the team start to burndown

Go overboard with “high ceremony” unless absolutely needed for your environment

Define a ‘just enough’ approach to improve upon where you are now.

Define a process and place it on a shelf or a hard drive for no one to ever see again

Use a tool that can ‘enact’ your

About the author

AgileConnection is a TechWell community.

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