EWITA
Project Start Date:
Project Finish Date:
ID |
Task Name |
Duration |
Predecessors |
26 |
Develop Consensus (repeat as necessary) |
2.38 days |
25 |
27 |
Schedule 4 Session Dates |
2 hrs |
25 |
28 |
Identify Players in consensus building meetings |
1 hr |
|
29 |
Set Agenda for Consensus Session |
3 hrs |
|
30 |
Run Consensus Meetings (repeat as necessary) |
2 days |
29 |
31 |
Prepare for Consensus Session |
2 days |
|
32 |
Conduct Consensus Session |
4 hrs |
|
33 |
Adopt meeting Rules |
1 hr |
|
34 |
Document Meeting |
1 day |
|
35 |
Publish on Web |
1 day |
|
36 |
Modify "Strawman Architecture" |
4 hrs |
|
37 |
Resolve Open issues |
2 days |
30 |
38 |
Document Open issues |
2 days |
|
39 |
Present Open issues to Project Sponsor |
2 hrs |
|
40 |
Modify "Strawman Architecture" |
1 day |
|
41 |
Publish Draft Architecture |
1 day |
37 |
42 |
Document Complete Architecture Definition |
1 day |
|
43 |
Publish Draft to Web |
4 hrs |
|
. |
. |
||
. |
. |
This task set is for the development of a consensus, this indicates that there is a group of enterprise wide "experts " in the IT area that may or may not be in the IT part of the enterprise. Strong leadership and backing of the Architecture reduces the amount of time developing consensus.