Assessing the Need for Change

You have defined the problem, proposed a solution, and looked at potential "deal breakers" to that solution in the dimensions of business, technology, and resources. If the solution appears feasible in all respects, you can bypass this step and proceed to risk assessment. However, if your feasibility study has uncovered problem areas, you have more work to do.

Long ago, an instructor told me that if you have an obstacle that stands in your way to accomplishing a goal, you have two choices: Give up on your goal, or figure out a way to get through the obstacle (see Figure 1.3).

Figure 1.3. Making choices.

graphics/01fig03.gif


This decision point is often where you find yourself at this stage of the Envisioning Phase. If the solution is determined not to be feasible in any of the three dimensions just discussed, you can plan your way around the obstacle or alter the business goalin this case, represented by the proposed scope.

This is the first time the business stakeholders and application architects have an opportunity to negotiate. Items that are not successfully negotiated often turn into risks (the next section of this chapter).

Do you have a workable solution that is at least feasible from the information you know at this stage of the project? Write it down and have all parties sign off.



Analyzing Requirements and Defining. Net Solution Architectures (Exam 70-300)
MCSD Self-Paced Training Kit: Analyzing Requirements and Defining Microsoft .NET Solution Architectures, Exam 70-300: Analyzing Requirements and ... Exam 70-300 (Pro-Certification)
ISBN: 0735618941
EAN: 2147483647
Year: 2006
Pages: 175

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net