All projects are managed against the triple constraints of time, cost and scope. Technology projects, however, come with their own additional constraints. In this video, Bob McGannon explores the common constraints that are specific to technology projects including the bridging from old to new technology, resource constraints and dealing with architectural standards.
- All projects are managed against the triple constraints…of time, cost, and scope.…However, technology projects are special and typically…come with additional constraints.…There are three common constraints specific…to technology projects.…Let's start with bridging the old technology to the new.…Your new system should be better and provide additional…value to your business.…However, sometimes data that's required in the new system…does not exist in the old.…
To address this constraint, you'll need to plan for…the creation of new data prior to implementation…or determine if you want to have the new data created slowly…over time as the new system is being used.…The advantage of creating the new data is that…there is no additional work to be performed by…the project team prior to implementation.…The disadvantage is the new data that could be valuable…to the business won't be available for…a considerable amount of time and it puts additional…burden on business resources to create that data.…
If you decide to create the data, you'll need to…
- Identify three characteristics of the ideal To Be process map.
- Summarize the steps to manage organizational change.
- Recognize three details to consider when evaluating a cloud solution.
- Recall the consequence of failing to address functionality gaps in a technical solution.
- Determine which facts to collect before discussing resource availability with sponsors.
- Identify the questions to ask when asking team members for feedback on milestone development.