This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
There is capability assessment done in Preleminary phase as well as Phase A. What's the difference between the 2 assessments? Is the Preliminary assessment just at a higher level?
Is the Preliminary Assessment optional? I can see the sponsor including upgrading the organizational's capability in the vision, and it makes sense to do a high level assesment in Prelim phase.
However, let's say the sponsor doesn't express a need in terms of upgrading the organization's capability; (we know we can do it it, we just want to do it differrently), do you just skip the Prelim assessment , and do it during Phase A
I'm trying to apply TOGAF to a project at work. Basically, we have a CI server that runs automated build. We have configured builds that run on a daily and weekly basis and test differrent things. The problem is that the "daily" build takes couple of days to run . THey want me to go in and figure out what needs to be done to make the builds faster. It's an easy project actually, and the reason they have given it to me is to take me out of my comfort zone. I was thinking this is a nice place to practice TOGAF in. Differrent people already know what they are gonna do, but no one has the big picture in front of them. I thought, I can TOGAFy the whole process. It will help me find things that maybe other people have missed, and also I will be able to create a high level view of the entire test automation architecture.
So, right now, realistically, the project in on Prelim phase - Vision phase. People have already rushed ahead and have started implemnting stuff without planning the whole thing out. that's fine for now. I can;t make them wait so i can do TOGAF. SO, based on what I know now, we don't really need to train any of the people. They just need to start doing things differrently. So, can I just skip the Capability assessment in Prelim phase
In the preliminary phases, it is assessing your organization's ability to do architecture. In phase A, it is assessing for this particular project. If you were actually getting your organization on TOGAF, you can't skip the preliminary part. It sounds like your goal is to practice TOGAF. In which case, I would say that something is better than nothing.
I read somewhere that you can skip major artifacts in Scrum and then you aren't doing Scrum. You are doing something inspired by Scrum. I think that is the case here. You may not be doing TOGAF per se, but you are doing something like it/pieces of it. As long as you know more about TOGAF than you did at the start, this seems like a wise choice.
Ahhhh I get it. Thank you very much. In prelim phase you are picking your EA framework, and assessing you capability in using that framework, whereas starting from phase A you are picking your building blocks and assessing your capability with those building blocks. That makes perfect sense.
Yes, this iteration is just for practice. I've only told my boss that I'm doing this. Really, to do EA at my current company, it will have to be done by people one pay grade above me. They already do parts of it in an ad-hoc manner. I'm hoping to do this as a case study that I can present to my bosses. I'll have to skip some steps, so it will be heavily customized TOGAF, but for the steps I'm skipping, I'm making notes on why I skipped those steps, and what we will do if we did it for real.
author & internet detective