Head of Enterprise Architecture
Join the post-meetup discussion at ca. 16:45
The process can be agile, even if the enterprise is not (yet)
The transformation affects more than one layer of an enterprise, i.e. not just business model, organisation or IT but mostly all three together.
The scope of a transformation can be wide (e.g. changing the business model entirely) or narrow (e.g. introducing a new service that requires new technology and organisation)
In these situations you need a process that offers:
Coffee Lounge: What are the core aspects of agile transformation?
Create a shared
Use modern, collaborative tools
an agile transformation process
Have you involved all key stakeholders and got the right skills on board.
Do you have a common purpose regarding transformation?
Does your team understand the big picture?
Do you have the key enablers such as processes and tools in place?
Enterprise Ecosystem and Architecture
CxO, Domain Experts, Transformation Architects, Business Engineers, System Engineers...
Most organisations view themselves as "machines" - leading to over-specialisation and command and control structures.
When it comes to transformation teams, it is better to view organisations as living organisms - ensure that your transformation team bridges organisational boundaries
What cultural struggles do you experience in your company?
Coffee Lounge: How did you experience the transformation to agile?
Enterprise Transformation is a creative problem solving and design process, which starts with initial ideas and leads all the way to launching new products, services, organisations and systems into the market.
While there is clear progress along the phases, this is not a "waterfall process" – you need to implement the full transformation cycle right from the beginning.
Within each phase you run through at least one (but often more) transformation cycles, which are continuously reconfigured in an exploratory fashion.
Understand your current situation and develop an initial vision of what you want to achieve.
Do whatever you can to validate your ideas: build prototypes, engage stakeholders, work through the numbers.
Work out the details of what you want to achieve.
Build your solution, get ready for re-organisation and launching new products and services. Train your work force.
Launch your products and services, start living your new processes.
Analyze your situation. Explore "What if" questions, identify constraints and critical factors.
Define the principles which will guide your design. Look for patterns that may help you to find an "optimal" design. Identify and flesh out design alternatives.
Plan and organize the actual transformation. Prepare your stakeholders, train your workforce, communicate details of the transformation.
Create prototypes of the future to test your ideas against reality – models, simulations, mock-ups, apps & systems ... to shape and inform the transformation process.
Use a collaborative brainstorming tool for first exchange of ideas
Use predefined templates to channel the discussion
Use the visual result to communicate the outcome easily and informally to the stakeholders
Use a formal architecture model to keep the current state and the desired state of the company
Use a formal modeling language with clear semantics (e.g. archimate)
Use the model to evaluate the impact of changes to the entire enterprise
Use a flexible, collaborative ticketing and workflow engine to capture all tasks and channel them in the right direction
Ensure that nothing is forgotten
Track progress at all times
Coffee Lounge: Which agile, collaborative tools do you use?
BizzDesign Enteprise Studio
GmbH & Co. KG
+49 30 9203833320