Changes

When department has an idea, a problem or an issue that needs to be addressed, the <b>main</b> question that needs to be answered is that "<b><u>Is it worth it</b></u>?".

When department has an idea, a problem or an issue that needs to be addressed, the <b>main</b> question that needs to be answered is that "<b><u>Is it worth it</b></u>?".

To answer this question, department has to:<br>

To answer this question, department has to:<br><br>

1. <b>Identify the end goal</b>  

1. <b>Identify the end goal</b>, ie. benefits, business outcomes, alignment to strategy/mandate

* what is it that the department wants to achieve at the end ?

* what is it that the department wants to achieve at the end ?

* what problem is the department trying to solve ?

* what problem is the department trying to solve ?

* how would the new solution fit in the whole IT landscape within the department and the GC ?  

* what are the benefits being realized ?

* what are the measurable business outcomes ?

2. <b>Determine options</b> - if we use this solution:  

2. <b>Figuring out options</b> - if we use this solution:  

* how would it affect the outcome ?

* how would it affect the outcome ?

* how would it affect the existing process ?

* how would it affect the existing process ?

* how would it affect the other existing systems in the ecosystem ?  

* how would it affect the other existing systems in the ecosystem ?  

All these questions need to be considered through the architecture layers of B-I-A-T-S+P (Business - Information - Application - Technology - Security + Privacy).

 

 

All these questions need to be considered through the various lenses of architecture layers <b>B-I-A-T-S+P (Business - Information - Application - Technology - Security + Privacy)</b>.

<br><br>

<br><br>