Phases E, F and G

Owned by Selvyn Wright
Last updated: Apr 21, 2017

These notes are summary of the key points the phases E, F and G

In terms of covering these phases, visit these links for a summary of what we've covered so far

Key take aways for today are

In Phase E

  • Bring together all the gaps and roadmaps from BCD to construct consolidated roadmap (use the attached examples for roadmaps, we call them tube maps for road maps)
  • Select the SBBs that were identified in BCD
  • Decide on an implementation strategy - phased, big bang, incremental etc
  • Break your world up into a series of transition architectures - Oyster card example attached
  • Architects don't act alone in phase E, they work with the business to decide on the way forward, especially start working with the PMO early, gets their buy in
  • Review all the PESTLEs - a lot can change in short time, some things that were relevant in A are now irrelevant
  • This is the beginning of the implementation road, nothing gets signed of or finalised until phase F (think F for final)
  • Some of the suggested TOGAF® thinking I would say you're already doing when you're in earlier phases - costings, solutions, implementation strategies, assigning value to projects etc.

In Phase F

  • See it as a continuation of phase E but here you work closer with the PMO.
  • No one is asking you to be a PM but to help them coordinate their activities
  • Finalise all the architecture documents
  • The outpur from E and F should be information needed as input into the Architecture Contracts that are drawn up for Phase G
  • From the architects perspective, F is confirming their thinking, their envisioned programmes and projects with the PMO

In Phase G

  • Engage with the delivery team through an Architecture contract
  • Be careful how you read some of the wording in phase G, it can look like your doing stuff that you did in previous phases, no, it's about advising the delivery team on the enterprises priorities
  • Govern the work being done through reviews
  • It's up to the delivery team to decide on the best way to implement to solution, you can advise them on the enterprises priorities etc
  • There may be some risks that haven't been mitigated, these are called residual risks
  • Look at this example of a commercial company using TOGAF® 8 (we don't get many commercial give aways)