Presentation OverviewIntroductionsWhy EA?Overview of MethodologiesZachmanTOGAFFEAAgile EAVPEC-TSIPPutting Them TogetherSummary
Charles Edwards
Charles Edwards
I would make a on comment on this slide and that's that you may have missed (or chosen not to represent) a potential candidate called Lite Enterprise Architecture (www.liteEA.com) John Wu - from washington, who I believe has some good ideas.
AEA Essentials
Definitive Reference: agileea.wikidot.com mostly by Charles EdwardsMain Proponent: Charles Edwards
Focal Point: Agile TOGAFIntroduced: 2007
AE Goal: management and definition of the Architecture of the Enterprise (Business or set of businesses) that includes everything from the Business Strategy, down into the Business Operation Architecture (static and dynamic) for the purposes of optimizing the enterprise; the Information systems (made up of Applications, Services and Data) and the Technology and Infrastructure that this runs on. It also includes aspects such as Security, Data, People and Performance.
Charles Edwards
I would prefer you to use either 1.) www.AgileEA.com or secondly 2) Process.AgileEA.com - reason: I will shortly be changing the http://agileea.wikidot.com to a 3) Wiki.Agileea.com and have it all under one roof. This was (you guessed it) - an Agile way of getting from a to b!
Charles Edwards
Helped it's fair to say by a number of work peers and other EA collaborators, but unfortunately I've been finding it difficult to find "committers". If you know of people I'd really be keen for them to contribute.
Charles Edwards
Nore recently I now add "Servies" ino this mix too
AEA Ideas
Take the EA one month at a time (called “Sprints”.
Keep list of hot work items.
Daily status meetings (“Scrum Meetings”) to evaluate progress.
EA needs the agility that Scrum (agile development) provides.
Focus on time-boxing the AE process.
Charles Edwards
I'd prefer this to read "EA needs an entrenched concept of Adaptability, Agility, Continuous improvement, similar to what SCRUM (agile dev) provides."
Charles Edwards
What you say is correct, but it's a bit more than that - it's the iterations, but within a larger "Cyclic" or Phased approach where the EA "learn to Crawl, before you Walk, before you Run. After that they aim to produce a better product release regualrly - say every six months to a year. (Just like Cars, PC's, Mobile Phones or Aircarft models are released onto the market).
Charles Edwards
Within a "big picture" or "Phased" context
Charles Edwards
Daily in the small. Monthly in the medium. Yearly in the large. Cycles within cycles. EA is like making and refining a single product. The "Product" is the "Architecture" for the Enterprise. This product needs to be constantly improved, after all every other successful business does so with products for sale. The enterprise needs to do so with its Architecture to not only survive but to become dominant.
Charles Edwards
Organise the team and setup detailed expectations.Another idea- possibly not evident - is to organise the team members into "knowing what they have to do" in any particular situation.To define detailed "Roles" (not just job descriptions - too vague), to define specific "WorkProducts", and specific "Activities" that Produce these.
AEA Wrap-up
The goal of making TOGAF agile is good.
It is still not clear how AEA will achieve this.
Think of AEA as an evolving set of Best Practices for making TOGAF usable.
AEA is still in Beta
Charles Edwards
Yes - we are defining a scaled down version 1.0 that will be officially released as a baseline by the end of the year.
Charles Edwards
We like all the good work already done in togaf - do not want to re-invent the wheel. Just organise it a little better. Unfortuantely my experience is that despite the name TOGAF is not as open as it might seem. You have to pay huge amounts to join, then break into the inner circle to get your voice heard. Its was simply easier to go direct to the market.
Charles Edwards
Agreed. The beauty of Agile! Start with a goal and iterate towards it, minimising the Risks as you go. It has to be the shortest path from A to B.It will be acheived by persistance, the collaboration of those willing to join the groundswell, and some form of opensource critial mass.
Charles Edwards
As well as other methodologies, such as MODAF, FEAF, Zachman concepts, etc.Modernizing it by using concepts such as Scrum, UML modelling, BMM, Risk Management, Service Oriented Architecture (in the large - not just Web services)
Charles Edwards
I am collaborating with http://doriq.co.uk who are concentrating on building an underlying Meta-Model and related Toolset and we are merging the processes into alignment to offer a well rounded solution. Not just a stand alone bunch of processes. All opensource.
