Stakeholders
All activities of the application lifecycle involve different stakeholders, each of them focussing on different aspects of the overall development process.
For example:
- A developer wants to have early feedback on the code committed in the trunk stream (Continuous Integration) and wants to build the project in his IDE with the correct latest sources and common libraries.
- A project manager wants to have a clear overview of the project status: is the latest code in the trunk buildable? do the unit tests run successfully? what are the guys of QA testing? which is the current production version?
- Production operators prefer an automated deploy process, where they can control the environment variables?
- The CIO and CEO of a corporation would like to see an automated and repeatable process with an audit trail.
Implementing IKAN ALM to manage the application lifecycle, provides a series of benefits for each group of stakeholders without compromising the responsibility of the other groups.
| Stakeholder | Benefit |
|---|---|
| Development |
|
| Build and Release management |
|
| IT Management |
|
| CFO (Chief Financial Officer) |
|
| CEO (Chief Executive Officer) |
|
| External (shareholders, government, auditors) |
|
Next: Product



