Continuous Delivery of Agile ArchitectureBrad Appleton
by Brad Appleton, APLN Chicago 2018 Conference, April 2018,
Agile Development & DevOps have necessitated revisititing how architecture changes over time: collaboration, design thinking, technical debt, emergent design, evolutionary architecture, agile infrastructure, and continuous delivery have all played a key role in how we can integrate architecture into agile delivery methods.
This presentation explores proven ways to continuously plan, build & evolve software architectures to support continual change as part of the continuous value-delivery pipeline.
Ever wondered how Agile can be implemented in larger organisation/project. SAFe is the answer. In this session we will understand the core principles and values that is require to implement SAFe in larger organisation.
Capability models have a long history. They came out of business schools in the 50ies. In recent years the enterprise- and business architecture communities seem to have taken over, making capabilities more an IT rather than a business modeling concept. Most capability models we've seen fail to achieve their original purpose: to enable business people to design better enterprises - ones that are fit for purpose, efficient, adaptive to change and satisfy customers.
In this webinar, Wolfgang Goebl explains the typical flaws of capability models and design patterns for next-generation capability modeling. You will learn:
practical patterns to create capability maps that foster a seamless business & IT co-design
why most capability modeling efforts fail and how to overcome the usual problems
how to connect other elements of the architecture with capabilities - how to run a broad elicitation process with all relevant stakeholders
how to use capability maps in corporate management
In this session we will discuss the use of Agile constructs within the domain of software architecture. This will include an exploration of how to balance emergent designs with intentional planning. Additional ancillary topics will also be addressed including: common architecture principles, guidelines for measuring good architecture, and an evaluation of agile techniques.
By the end of the session, attendees will have a new perspective on architecture that will empower them to create flexible software solutions.
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
As we head into a new year, one thing is for sure, the world of technology and IT will continue to evolve and be disrupted at a frightening pace. The role of the modern IT organisation will thus need to adapt and be agile in order to keep pace with this changing landscape and to continue to be valuable to the organisations that they service. As IT estates become more complex, internal IT functions will need to become more mature and efficient in the way they operate in order to be perceived as a valued asset to the business. The release of IT4IT at the end of last year provides an interesting and potentially highly valuable reference architecture for IT organisations to use to help achieve this level of maturity and efficiency.
The IT4IT standard has really started to pick up momentum as we start 2016 and it is great to see the increase in the membership of the IT4IT forum as well as the general interest that is being seen in the industry for this new standard. I recently co-presented a webinar in collaboration with the Open Group where we looked at the potential real-world application and benefits that IT4IT can offer. Mandate and mindset will be critical to the successful use of IT4IT but I am confident that this approach has the potential to be very beneficial for many organisations as the role of the IT function continues to be redefined.
Continuous Delivery of Agile ArchitectureBrad Appleton
by Brad Appleton, APLN Chicago 2018 Conference, April 2018,
Agile Development & DevOps have necessitated revisititing how architecture changes over time: collaboration, design thinking, technical debt, emergent design, evolutionary architecture, agile infrastructure, and continuous delivery have all played a key role in how we can integrate architecture into agile delivery methods.
This presentation explores proven ways to continuously plan, build & evolve software architectures to support continual change as part of the continuous value-delivery pipeline.
Ever wondered how Agile can be implemented in larger organisation/project. SAFe is the answer. In this session we will understand the core principles and values that is require to implement SAFe in larger organisation.
Capability models have a long history. They came out of business schools in the 50ies. In recent years the enterprise- and business architecture communities seem to have taken over, making capabilities more an IT rather than a business modeling concept. Most capability models we've seen fail to achieve their original purpose: to enable business people to design better enterprises - ones that are fit for purpose, efficient, adaptive to change and satisfy customers.
In this webinar, Wolfgang Goebl explains the typical flaws of capability models and design patterns for next-generation capability modeling. You will learn:
practical patterns to create capability maps that foster a seamless business & IT co-design
why most capability modeling efforts fail and how to overcome the usual problems
how to connect other elements of the architecture with capabilities - how to run a broad elicitation process with all relevant stakeholders
how to use capability maps in corporate management
In this session we will discuss the use of Agile constructs within the domain of software architecture. This will include an exploration of how to balance emergent designs with intentional planning. Additional ancillary topics will also be addressed including: common architecture principles, guidelines for measuring good architecture, and an evaluation of agile techniques.
By the end of the session, attendees will have a new perspective on architecture that will empower them to create flexible software solutions.
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
As we head into a new year, one thing is for sure, the world of technology and IT will continue to evolve and be disrupted at a frightening pace. The role of the modern IT organisation will thus need to adapt and be agile in order to keep pace with this changing landscape and to continue to be valuable to the organisations that they service. As IT estates become more complex, internal IT functions will need to become more mature and efficient in the way they operate in order to be perceived as a valued asset to the business. The release of IT4IT at the end of last year provides an interesting and potentially highly valuable reference architecture for IT organisations to use to help achieve this level of maturity and efficiency.
The IT4IT standard has really started to pick up momentum as we start 2016 and it is great to see the increase in the membership of the IT4IT forum as well as the general interest that is being seen in the industry for this new standard. I recently co-presented a webinar in collaboration with the Open Group where we looked at the potential real-world application and benefits that IT4IT can offer. Mandate and mindset will be critical to the successful use of IT4IT but I am confident that this approach has the potential to be very beneficial for many organisations as the role of the IT function continues to be redefined.
Stepping-stones of enterprise-architecture: Process and practice in the real...Tetradian Consulting
What do we do when we’re doing enterprise architecture? What issues do we tackle, in what sequence, for what business reasons, for what business value? And how do we get results fast? This presentation describes how to adapt the Architectural Development Method (ADM) from The Open Group Architecture Framework (TOGAF) for use in all types of enterprise architecture - for IT and beyond - and at all architecture maturity-levels.
[Presentation at TOGAF Conference, London, April 2009. Applies to TOGAF versions 8.1 and 9. Copyright (c) Tetradian Consulting 2009]
It is well known that an effective PMO is key to successful and efficient program and project execution. In other words, doing things “right”. Enterprise Architecture is the discipline that plans and monitors enterprise transformation and aligns the business strategy with information technology capabilities. In other words, doing the “right things” to support the business.
Why is it organizations despite having both of these disciplines still struggle with effective enterprise transformation? What can we done to use these disciplines more effectively to effect better business outcomes? What are the roles of each discipline and how do they work together to create business value?
In this presentation, Riaz will address these questions and will provide real life examples that can help build a strong relationship between the PMO and Enterprise Architecture.
Learning Objectives:
• How to build a strong relationship between the PMO and Enterprise Architecture (EA) to deliver positive outcomes for your organization
• Identify the different roles and functions of the PMO and EA as well as their similarities
Introduction to SAFe, the Scaled Agile Frameworksrondal
Sans doute vous identifiez vous dans une ou plusieurs des situations suivantes:
- plusieurs équipes Scrum travaillent dans votre entreprise, parfois sur un même projet ou des projets connexes
- la coordination entre équipes Scrum n'est pas optimale
- vous-même, ou certains stakeholders, ont besoin d'une vue plus long terme sur vos projets Agile, plus que "juste le prochain sprint"
- sur base du succès de Scrum dans votre entreprise, vous voulez allez plus loin et vous voulez rendre plus agile l'entièreté de votre entreprise
Si c'est le cas, venez découvrir le framework SAFe.
Après une présentation du framework et de ses fondements, vous serez en mesure de mieux le comprendre, et de voir ce qu'il peut apporter ou non à votre entreprise.
Future Proofing Your IT Operating Model for DigitalDavid Favelle
Having worked with Operating Model for over 10 years, Dave has new adopted DevOps, IT4IT and Continuous Delivery alongside traditional frameworks. The concept of the value stream is central to the thinking. The presentation was delivered as a Keynote at the Open Group in Amsterdam October 2017 -https://www.youtube.com/watch?v=Y7yH1JJKvqc&t=1969s
Note that Dave and the ValueFlow team deliver Operating Model on the ServiceNow platform.
Tool Kit: Business Analysis product (artefact) checklistdesigner DATA
Methodology is a toolkit not a process – Choose wisely
Methodologies contains many tools and techniques, such as, process, data , use case and class modelling, sequence diagramming and state transition diagramming, prototyping and report templates.
Not all these tools have to be used for every project.
So choose wisely and create your own fast path routes for completing different types of projects by preparing your own Business Analysis Project Planning Map. Build on your experiences and fine tune your product each time you undertake a new assignment.
http://www.tdan.com/view-articles/6089
Creating Enterprise Value from Business Architectureiasaglobal
This presentation will cover the Why (Value) and How (Execution) of a Business Architecture program. You will understand how you can lead your enterprise towards its vision by planning for key Business Capabilities that will get you there.
The TOGAF® Architecture Development Method recommends that "an architecture description be encoded in a standard language". As the Open Group standard for enterprise modeling, Archimate is a strong candidate for this role. This presentation will explore how a diversified financial services company selected and is using Archimate for its TOGAF® implementation. The speaker will compare available enterprise modeling languages and explain why Archimate was selected, and will explain how his organization developed an enabling metamodel and diagram templates using a leading enterprise modeling tool. Methodology transition will also be covered, including how existing diagram types were mapped to TOGAF®, and how TOGAF® diagram content was mapped to Archimate.
Delivered at February 2011 Open Group San Diego Conference
Scaling Agile With SAFe (Scaled Agile Framework)Andreano Lanusse
Apresentação feita no Agile in Rio, mostrando como um conjunto de 5 à 10 equipes ágeis podem entregar objetivos em comum usando Scaled Agile Framework® ou SAFe, e como iniciar o lançamento de um Agile Release Train.
During last few years, role of Enterprise Architecture has expanded from technical to strategic in an Organization. This slide deck presents: Using Enterprise Architecture in your Organization.
Value analysis with Value Stream and Capability modelingCOMPETENSIS
The new Archimate 3.1 has improved the strategy layer with major modeling objects related to value analysis: value stream and capability.
These objects are linked and answer major questions :
- [VALUE STREAM] What value do we deliver to customers ? What value do we want to deliver to customers ? This is the enterprise business model.
- [CAPABILITY] What operational model do we need to deliver value ? The capability model describes the operational model required to deliver value to customers.
You cannot succeed to transform a business model, enterprise activities without considering Value Stream & Capability analysis. Technology considerations are necessary but not sufficient.
Feel free to contact if you wish to get more support with your transformation projet.
Scalability is currently a big topic in the agile world. Most agile methods and practices often reach their limits when one wants to “agilize" more than a few teams, let alone one wants to achieve real agile collaboration of several hundert people.
The main problem is that many agile methods focus on the team. Kanban follows a completely different path - Kanban is not a team method! Kanban is a management method which focuses on generating value. "Manage work and not workers" is one of the key messages of the Lean Kanban management philosophy. Therefore, scalability is not a real topic within Kanban: if you focus on value generation of work, scaling Kanban simple means doing more Kanban - it’s inherent scalable.
In this session I show how one could use Kanban at scale. Besides the general schematic explanation I will also show a case study where Kanban is used to coordinate work of more than 200 people.
Stepping-stones of enterprise-architecture: Process and practice in the real...Tetradian Consulting
What do we do when we’re doing enterprise architecture? What issues do we tackle, in what sequence, for what business reasons, for what business value? And how do we get results fast? This presentation describes how to adapt the Architectural Development Method (ADM) from The Open Group Architecture Framework (TOGAF) for use in all types of enterprise architecture - for IT and beyond - and at all architecture maturity-levels.
[Presentation at TOGAF Conference, London, April 2009. Applies to TOGAF versions 8.1 and 9. Copyright (c) Tetradian Consulting 2009]
It is well known that an effective PMO is key to successful and efficient program and project execution. In other words, doing things “right”. Enterprise Architecture is the discipline that plans and monitors enterprise transformation and aligns the business strategy with information technology capabilities. In other words, doing the “right things” to support the business.
Why is it organizations despite having both of these disciplines still struggle with effective enterprise transformation? What can we done to use these disciplines more effectively to effect better business outcomes? What are the roles of each discipline and how do they work together to create business value?
In this presentation, Riaz will address these questions and will provide real life examples that can help build a strong relationship between the PMO and Enterprise Architecture.
Learning Objectives:
• How to build a strong relationship between the PMO and Enterprise Architecture (EA) to deliver positive outcomes for your organization
• Identify the different roles and functions of the PMO and EA as well as their similarities
Introduction to SAFe, the Scaled Agile Frameworksrondal
Sans doute vous identifiez vous dans une ou plusieurs des situations suivantes:
- plusieurs équipes Scrum travaillent dans votre entreprise, parfois sur un même projet ou des projets connexes
- la coordination entre équipes Scrum n'est pas optimale
- vous-même, ou certains stakeholders, ont besoin d'une vue plus long terme sur vos projets Agile, plus que "juste le prochain sprint"
- sur base du succès de Scrum dans votre entreprise, vous voulez allez plus loin et vous voulez rendre plus agile l'entièreté de votre entreprise
Si c'est le cas, venez découvrir le framework SAFe.
Après une présentation du framework et de ses fondements, vous serez en mesure de mieux le comprendre, et de voir ce qu'il peut apporter ou non à votre entreprise.
Future Proofing Your IT Operating Model for DigitalDavid Favelle
Having worked with Operating Model for over 10 years, Dave has new adopted DevOps, IT4IT and Continuous Delivery alongside traditional frameworks. The concept of the value stream is central to the thinking. The presentation was delivered as a Keynote at the Open Group in Amsterdam October 2017 -https://www.youtube.com/watch?v=Y7yH1JJKvqc&t=1969s
Note that Dave and the ValueFlow team deliver Operating Model on the ServiceNow platform.
Tool Kit: Business Analysis product (artefact) checklistdesigner DATA
Methodology is a toolkit not a process – Choose wisely
Methodologies contains many tools and techniques, such as, process, data , use case and class modelling, sequence diagramming and state transition diagramming, prototyping and report templates.
Not all these tools have to be used for every project.
So choose wisely and create your own fast path routes for completing different types of projects by preparing your own Business Analysis Project Planning Map. Build on your experiences and fine tune your product each time you undertake a new assignment.
http://www.tdan.com/view-articles/6089
Creating Enterprise Value from Business Architectureiasaglobal
This presentation will cover the Why (Value) and How (Execution) of a Business Architecture program. You will understand how you can lead your enterprise towards its vision by planning for key Business Capabilities that will get you there.
The TOGAF® Architecture Development Method recommends that "an architecture description be encoded in a standard language". As the Open Group standard for enterprise modeling, Archimate is a strong candidate for this role. This presentation will explore how a diversified financial services company selected and is using Archimate for its TOGAF® implementation. The speaker will compare available enterprise modeling languages and explain why Archimate was selected, and will explain how his organization developed an enabling metamodel and diagram templates using a leading enterprise modeling tool. Methodology transition will also be covered, including how existing diagram types were mapped to TOGAF®, and how TOGAF® diagram content was mapped to Archimate.
Delivered at February 2011 Open Group San Diego Conference
Scaling Agile With SAFe (Scaled Agile Framework)Andreano Lanusse
Apresentação feita no Agile in Rio, mostrando como um conjunto de 5 à 10 equipes ágeis podem entregar objetivos em comum usando Scaled Agile Framework® ou SAFe, e como iniciar o lançamento de um Agile Release Train.
During last few years, role of Enterprise Architecture has expanded from technical to strategic in an Organization. This slide deck presents: Using Enterprise Architecture in your Organization.
Value analysis with Value Stream and Capability modelingCOMPETENSIS
The new Archimate 3.1 has improved the strategy layer with major modeling objects related to value analysis: value stream and capability.
These objects are linked and answer major questions :
- [VALUE STREAM] What value do we deliver to customers ? What value do we want to deliver to customers ? This is the enterprise business model.
- [CAPABILITY] What operational model do we need to deliver value ? The capability model describes the operational model required to deliver value to customers.
You cannot succeed to transform a business model, enterprise activities without considering Value Stream & Capability analysis. Technology considerations are necessary but not sufficient.
Feel free to contact if you wish to get more support with your transformation projet.
Scalability is currently a big topic in the agile world. Most agile methods and practices often reach their limits when one wants to “agilize" more than a few teams, let alone one wants to achieve real agile collaboration of several hundert people.
The main problem is that many agile methods focus on the team. Kanban follows a completely different path - Kanban is not a team method! Kanban is a management method which focuses on generating value. "Manage work and not workers" is one of the key messages of the Lean Kanban management philosophy. Therefore, scalability is not a real topic within Kanban: if you focus on value generation of work, scaling Kanban simple means doing more Kanban - it’s inherent scalable.
In this session I show how one could use Kanban at scale. Besides the general schematic explanation I will also show a case study where Kanban is used to coordinate work of more than 200 people.
Chaos Engineering is the technique to simulate chaos and havoc in the live environment, which the engineers use to create a fault tolerant application. In the session we will talk about some of these scenarios and Chaos Mesh, a tool for Chaos engineering on Kubernetes.
Correlation of simulation_models_using_concept_modelingSalvatore Scalera
Pre-requisite for efficient vehicle programs is the CAE driven development process. The accuracy of the models increases over time and leads to an increasing amount of available Concept models in databases. Due to the
increased acceleration of the development process, these models are critical in providing direction on vehicle architecture in the early stages of a program.
Due to the high importance of these decisions it is mandatory to trust the results of this early CAE models. Correlation of this Concept models to test or
reference mainstream CAE models creates the confidence in this approach. The correlation focuses on two aspects: 1. the level of detail required to capture
the detailed folding characteristic of the structure (e.g. siderail or B-Pillar) and 2. the process chain used to process the raw output from SFE Concept into
RADIOSS Include files (e.g. gap, contacts, spot-welding, adhesives, bolts). This process chain is implemented using HyperMesh in batch mode, details may
be found in [4]. This process chain is tuned to latest program modeling approaches and to meet the desired correlation status.
In this presentation RADIOSS safety concept models are correlated to different impact modes. Tools and methods are explained focusing on both the
automated evaluation of simulation output and the judgment of the correlation quality.
Software Architecture: views and viewpointsHenry Muccini
This is an introductory lecture to Software Architecture Views and Viewpoints, part of the Advanced Software Engineering course, at the University of L'Aquila, Italy (www.di.univaq.it/muccini/SE+/2012)
AOTB2014: Agile Testing on the Java PlatformPeter Pilgrim
Creative Commons 2.0 License
Attribution-NonCommercial-ShareAlike 2.0 UK: England & Wales (CC BY-NC-SA 2.0 UK)
https://creativecommons.org/licenses/by-nc-sa/2.0/uk/
Share — copy and redistribute the material in any medium or format
Adapt — remix, transform, and build upon the material
The licensor cannot revoke these freedoms as long as you follow the license terms.
This talk about the following:
* TDD
** Is TDD Dead?
** David Heinemeier-Hanson and the controversy
* Java Technology
** If only JUnit tests were this simple
** Java has a some great static analysis tools
** Unfortunatley, these do not work too well in Scala platform
** Guidelines to write tests
* Creative Development in Principle
** Design is a balance
** Inventing your own style
** Avoid lock-in with TDD, use it instead as a design tool
* Scala Technology
** Scala Option
** Function objects
** Pattern matching
** Avoid if and then else and null pointers
* Legacy
** Final advice
This talk was given by Peter Pilgrim, invited speaker to the Agile On The Beach conference on the 5th September, 2014 at Penryn Campus, University of Exeter, Cornwall
By demystifying Agile constructs, and how architects fit into the
development process, organizations can find and follow best practices
and deliver benefits that advance accelerated coding objectives and
meet strategic business needs.
8. Principles of Agile Architecture
1. The teams that code the system design the system
2. Build the simplest architecture that can possibly work
3. When in doubt, code it out
4. They build it, they test it
5. The bigger the system, the longer the runway
6. System architecture is a role collaboration
7. There is no monopoly on innovation
8. Implement architectural flow
8
11. Architecture is role collaboration
Architectural
inputs,
ideas,
constraints
Architectural Evolution
11
12. Building Architecture Runway
Theme 1 Solution Epics
Epic Epic Epic Architecture features, in which the
1 2 5 Solution features depends on.
A
r
c
Epic 3
h Solution features without
E
i dependency on arch feature.
p
t
i
e Epic 4 Architecture features without
c
c dependency from solution features.
s
t
u Solution feature
r Epic 6
Arch feature
e
Note : No time dimension is illustrated in this picture.
12
13. Building Architecture Runway
3. Update
1. Determine initial component-based
architecture that will influence the eventual
formation of the application teams.
Architects /
Technical
iterate leaders
If uncertainty
high & risky
Feedback
2. Prototyping (Optional)
13
14. Extending Architecture Runway
3. Update
Spikes that
cannot resolved
“program” spikes
1. Identify story : design spikes, refactoring within a team
into iteration
required, evaluations & dependencies.
2. Determine what features the system iterate
may require in upcoming release plan
that are not presently supported by
architecture.
Architects /
Technical
iterate leaders
14
15. State Machine for Architectural Epic Kanban Model
2
Portfolio Disruptive Backlog
Roadmap technology
Technology
Roadmap criteria met, not ready
slot avail.
further
value/effort>X, 3 review
1 rejected slot avail.
Funnel Analysis
Trash
rejected
rejected
4 business case
approved &
Implementation resource available
Solution Common
problem usage model
15
16. One of the more insidious and persistent myths of agile development
is that up-front architecture and design are bad; that you should never
spend time up front making architectural decisions. That instead you
should evolve your architecture and design from nothing, one test-
case at a time.
Pardon me, but that’s Horse Shit.
(...)
Don’t feel that TDD is the only way to design. On the other hand,
don’t let yourself get too vested in your designs. Allow TDD to change
your plans if it leads you in a different direction.
Robert C. Martin, ObjectMentor blog, „The Scatalogy of Agile
Architecture”, 25.04.2009
17
