Development teams and operations (DEVOPS) are at the heart of the digital revolution. By sticking to the DEVOPS vision, the entire software factory can acquire more agility and sprints become more efficient. But why should architects be out of the picture? Wouldn’t it be a win-win for everyone if architects also became agile and collaborate with DEVOPS teams?
The “ivory tower” architect era is over
By not sharing their plans, Architects may unwillingly slow down development cycles and software deliveries. Or by sharing plans only at inappropriate times, unsynched with the devops cycle, collaboration is minimal and inefficient. The agile architect cannot stick to building rules from the outside hoping they are applicable!. So how to benefit from agile architecture?
- Share your vision by being at the right place at the right time in the software lifecycle.
- Use documented architecture models, versioned and updated thanks to the two-way integration between Axellience Agile Architecture Factory™ and Confluence.
- Participate using the right – and light – tools combining architecture and project management to have a global vision (JIRA for example)
- Integrate your work with DEVOPS teams to align your needs and move in the same direction together.
Speed does not mean backlash, disorder and chaos
You don’t want to keep the DEVOPS teams waiting. Do you prefer to run after developers and project managers to feed your documentation afterwards (after release developments and deployments) and often with errors due to the asynchronous nature of the process? So how can you leverage an agile architecture approach?
- Integrate into the development cycle and guide teams as they go along. A Jira ticket, 4-5 architecture model tunings and developers can move ahead, focusing only on the necessary, perfectly identified and tracked changes in order to produce a new release.
- Integrate and automate document production throughout the chain with tools that interoperate with each other such as Axellience Agile Architecture Factory™ and Confluence.
Never lose sight of the big picture
Jump back in the enterprise software lifecycle and housekeeping processes, for both legacy and new projects. As long as architecture dependencies are under control, any component change won’t bring regressions and bad surprises. Such dependencies are available from 3 viewpoints:
- From Confluence: Document-driven vision of architecture models versions
- From Jira: Requirement, change requests, impact analysis and bidirectional links with architecture models
- From Agile Architecture Factory™: integrated vision of IS architecture, components, dependencies and linked requirements.
Agile Architecture Factory™ repository has easy version management features which automatically syncs with Atlassian’s Jira and Confluence.
Be flexible! Agility requires flexibility, and above all a never ending dialog. Agile Architecture Factory™ is natively collaborative, and so are Jira and Confluence. The two-way integration between these tools gives total flexibility to the architecture teams and allows them to collaborate with DevOps teams, allowing architects to prove their value in an agile process.