Hey, where's the option for 'a legally binding document that requires the architecture team to deliver something amazing... or else'? Now that would be a real architecture contract!
I think Option C hits the nail on the head. The contract is about establishing the guidelines and ground rules for developing the enterprise architecture. Keeps everyone on the same page.
Haha, Option D is totally off base. A timeline? That's not what an architecture contract is all about. Maybe the test writer was having a bit of fun with that one.
I was leaning towards Option B, but after reading it again, I'm not so sure. Communicating the architecture info is important, but I don't think that's the primary role of the contract.
Option A sounds about right. The architecture contract is an agreement between the key stakeholders on what the architecture deliverables will be. Seems pretty straightforward to me.
Val
1 months agoJacklyn
6 days agoDahlia
17 days agoAleta
1 months agoGlendora
1 months agoBrittney
8 days agoMarguerita
15 days agoMona
19 days agoAlise
2 months agoPeter
14 days agoAmmie
24 days agoDoyle
1 months agoLeslee
2 months agoBoris
2 months agoRoyce
2 months agoAnthony
17 days agoCristina
18 days agoMarta
29 days agoFrankie
1 months agoKarma
1 months agoClorinda
2 months agoMelissia
2 months agoWilford
2 months agoLeslee
2 months agoDick
2 months agoCarmen
3 months agoDick
3 months ago