All projects are divided into phases, and all projects, large or small, have a similar life cycle structure. At a minimum, a project will have a beginning or initiation phase, an intermediate phase or phases, and an ending phase. The number of phases depends on the project complexity and the industry. For example, information technology projects might progress through phases such as requirements, design, program, test, and implement. All the collective phases the project progresses through in concert are called the project life cycle.
The end of each phase allows the project manager, stakeholders, and project sponsor the opportunity to determine whether the project should continue to the next phase. In order to progress to the next phase, the deliverable from the phase before it must be reviewed for accuracy and approved. As each phase is completed, it’s handed off to the next phase. You’ll look at handoffs and progressions through these phases next.
Handoffs
Project phases evolve through the life cycle in a series of phase sequences called handoffs, or technical transfers. The end of one phase sequence typically marks the beginning of the next. However, the completion of one phase does not automatically signal the beginning of the next phase. For example, in the construction industry, feasibility studies often take place in the beginning phase of a project.
The purpose of the feasibility study is to determine whether the project is worth undertaking and whether the project will be profitable to the organization. A feasibility study is a preliminary assessment of the viability of the project; the viability or perhaps marketability of the product, service, or result of the project; and the project’s value to the organization. It might also determine whether the product, service, or result of the project is safe and meets industry or governmental standards and regulations. The completion and approval of the feasibility study triggers the beginning of the requirements phase, where requirements are documented and then handed off to the design phase, where blueprints are produced. The feasibility might also show that the project is not worth pursuing and the project is then terminated; thus, the next phase never begins.
Phase Completion
You will recognize phase completion because each phase has a specific deliverable, or multiple deliverables, that marks the end of the phase. A deliverable is an output that must be produced, reviewed, and approved to bring the phase or project to completion. Deliverables are tangible and can be measured and easily proved. For instance, a hypothetical deliverable produced in the beginning phase of a construction industry project would be the feasibility study.
Deliverables might also include things such as design documents, project budgets, blueprints, project schedules, prototypes, and so on. This analysis allows those involved with the opportunity to determine whether the project should continue to the next phase. The feasibility study might show that environmental impacts of an enormous nature would result if the construction project were undertaken at the proposed location. Based on this information, a go or no-go decision can be made at the end of this phase. The end of a phase gives the project manager the ability to discover, address, and take corrective action against errors discovered during the phase.
Sometimes phases are overlapped to shorten or compress the project schedule. This is called
fast tracking. Fast tracking means that a later phase is started prior to completing and approving the phase, or phases, that come before it. This technique is used to shorten the overall duration of the project.
Most projects follow phase sequences within a project life cycle and, as a result, have the following characteristics in common: In the beginning phase, which is where the project is initiated, costs are low, and few team members are assigned to the project. As the project progresses, costs and staffing increase and then taper off at the closing phase. The potential that the project will come to a successful ending is lowest at the beginning of the project; its chance for success increases as the project progresses through its phases and life cycle stages. Risk is highest at the beginning of the project and gradually decreases the closer the project comes to completion.
Stakeholders have the greatest chance of influencing the project and the characteristics of the product, service, or result of the project in the beginning phases and have less and less influence as the project progresses. This same phenomenon exists within the project management processes as well.
Showing posts with label phase. Show all posts
Showing posts with label phase. Show all posts
Friday, July 3, 2009
Project Phases and Project Life Cycles
Topics:
handoffs,
life cycle,
phase,
track
Tuesday, August 7, 2007
Work Breakdown Structure Templates
Like a map that shows you the entire world at a glance, the Work Breakdown Structure (WBS) is a graphical representation of the entire work effort of a project. It is a deliverable-oriented grouping of project components that is used to:
To determine similarities in the two project life cycles, look at the project phases of the two projects. Are the phases the same or similar? Do the projects have the same number of phases? Are the phases in each project named differently but accomplish the same thing?
If the answer to any one of these questions is "no," you can't use the WBS from the past project as a template, and you don't need to do any further research. However, if the answer to all three questions is "yes," you can probably use the past project's WBS as a template for the new project.
If the project phases of two projects are similar enough that the WBS from the older project can be used as a template, the project manager should then look at each projects' deliverables to see if they are the same in number and similar in outcome. Although the deliverables may be project-specific, project managers can consider them similar as long as they are accomplishing similar tasks.
In summary, when comparing past projects to the current project to determine if you can use the WBS template from the previous project, you should look for similar life cycles, phases, phase outcomes, deliverables, and deliverable outcomes. If a previous and a new project have the same or similar project life cycles, phases, deliverables, and outcomes, save yourself time and money and reuse the WBS from the previous project.
- organize and define the total scope of the project
- confirm a common understanding of the project scope.
- Project life cycle. Organizations usually create a framework that all project managers follow when developing projects. This framework is known as a project life cycle. The project life cycle defines the beginning and the end of a project. Project life cycles are usually organization specific.
- Project phase. A project life cycle is broken down into phases that make it easier for a project manager to manage a project. Each project phase contains related project activities, usually culminating in the completion of a major part of the product or service.
- Project deliverable. Each project phase is broken down into deliverables, which helps the project manager to control the project. A project deliverable is any measurable, tangible, verifiable outcome, result, or item that must be produced to complete a project or part of a project.
- planning—understanding the proposed product or service
- designing—creating a detailed plan
- manufacturing—building the product or developing the service
- testing—making sure that the project or service meets expectations.
To determine similarities in the two project life cycles, look at the project phases of the two projects. Are the phases the same or similar? Do the projects have the same number of phases? Are the phases in each project named differently but accomplish the same thing?
If the answer to any one of these questions is "no," you can't use the WBS from the past project as a template, and you don't need to do any further research. However, if the answer to all three questions is "yes," you can probably use the past project's WBS as a template for the new project.
If the project phases of two projects are similar enough that the WBS from the older project can be used as a template, the project manager should then look at each projects' deliverables to see if they are the same in number and similar in outcome. Although the deliverables may be project-specific, project managers can consider them similar as long as they are accomplishing similar tasks.
In summary, when comparing past projects to the current project to determine if you can use the WBS template from the previous project, you should look for similar life cycles, phases, phase outcomes, deliverables, and deliverable outcomes. If a previous and a new project have the same or similar project life cycles, phases, deliverables, and outcomes, save yourself time and money and reuse the WBS from the previous project.
Thursday, July 5, 2007
The Rollout Phase of the IT Project
The final phase of the IT project life cycle, the rollout phase, ensures that the delivery of the new system to the clients will proceed smoothly and on schedule. The steps you should follow to successfully complete the rollout phase are described below.
1. Identify the inputs.
In the first step of the rollout phase, you should identify the following inputs.
The next step in the rollout phase is to conduct the key activities. The key activities associated with this phase are described below.
The PM must next create the outputs. The first output of this phase is change requests, which document any enhancement to the system and any problems encountered. The second output, post conversion review document, outlines how the conversion of the system went.
4. Meet the milestone.
Once the post conversion review document is completed, the PM completes the last step of the rollout phase—meet the milestone—by obtaining the post conversion review document sign-off from the conversion team and end users. This shows that the system was successfully converted.
Rollout is the final phase a project manager conducts in the IT project life cycle. Upon completion of the rollout phase, the PM has a successful project, and the client has a satisfactory product.
1. Identify the inputs.
In the first step of the rollout phase, you should identify the following inputs.
- Conversion plan. The conversion plan documents indicate any equipment needed to perform the conversion, when the conversion will take place, a time limit for performing the conversion, and any special requirements needed.
- Operations instructions. The operations instructions explain in detail how to install and use the system.
- Rollout plan. The rollout plan is a detailed schedule of the sites to be converted, the order of conversion, and the timing of the conversion.
- End user documentation. The end user documentation is anything the user will need to use the system correctly. It may be in the form of user manuals, operating instructions, tutorials, or access to a help facility.
The next step in the rollout phase is to conduct the key activities. The key activities associated with this phase are described below.
- Perform a readiness check. A readiness check is a series of checks the project manager (PM) and project management team make to mitigate risks associated with conversion and to confirm that user personnel have been trained properly. There are two types of readiness checks. The operational readiness check will ensure that the physical environment is correct and will verify that the architecture will support the new system. The user assurance check tests end users on the functionality of the new system in a controlled environment to verify that they have been trained properly.
- Conduct the system conversion. The next key activity, conduct the system conversion, involves converting the application from the old system to the new one.
- Perform production monitoring. The perform production monitoring key activity involves following the plans and delivering the materials that were developed in previous phases of the project life cycle to the end users.
- Document potential enhancements. The last key activity, document potential enhancements, is conducted after the end user tests the system. During the system conversion, end users identify corrections and improvements for the system, which the PM documents.
The PM must next create the outputs. The first output of this phase is change requests, which document any enhancement to the system and any problems encountered. The second output, post conversion review document, outlines how the conversion of the system went.
4. Meet the milestone.
Once the post conversion review document is completed, the PM completes the last step of the rollout phase—meet the milestone—by obtaining the post conversion review document sign-off from the conversion team and end users. This shows that the system was successfully converted.
Rollout is the final phase a project manager conducts in the IT project life cycle. Upon completion of the rollout phase, the PM has a successful project, and the client has a satisfactory product.
Topics:
conversion,
customer,
operational,
phase,
rollout
Wednesday, July 4, 2007
The Testing Phase of an IT Project
The testing phase of the IT project life cycle ensures that all requirements are met. Work conducted at this stage includes verifying that the functions are performed accurately, that the system works with all interfacing systems, and that the new system meets quality and/or standard requirements.
During the testing phase, the project manager (PM) must understand each of the components to monitor the process, but doesn't actually have to take part in completing the phase. The testing phase involves the following steps.
1. Identify the inputs.
In the first step of the test phase, you should identify the following inputs.
The next step, identify the tools, involves tools that will be used to test the system and track the results. Standard tools, such as word processing software, presentation and spreadsheet tools, and the specialized tools shown below, can be used in the testing phase.
The third step of the testing phase is to conduct the key activities shown below.
Design the testing approach. The purpose of this activity is to prepare for the testing that takes place. First you need to determine the level of testing and then the types of testing.
The next step in the testing phase, obtain the desired outputs, involves obtaining the test results, which are used as evidence that all the planned cycles have run successfully and that all outstanding issues have been resolved.
4. Meet the milestones to complete this phase.
In the final step, the PM obtains a conversion readiness sign-off form from the stakeholders of the project. This is the milestone that needs to be met for this phase of the project.
The testing phase ensures that the product meets all requirements and increases the chances of a successful project. Once it is completed, the project can move on to the final phase of the IT project life cycle—the rollout phase.
During the testing phase, the project manager (PM) must understand each of the components to monitor the process, but doesn't actually have to take part in completing the phase. The testing phase involves the following steps.
1. Identify the inputs.
In the first step of the test phase, you should identify the following inputs.
- Corporate IT standards. The corporate standards are used to determine the set of testing tools to be used for the different stages of testing.
- Conversion plan. The conversion plan specifies the order in which parts of the application will be implemented and the functionality corresponding to each release.
- Data conversion process. The data conversion process documents the design of the application required to create the databases for the system.
- Design document. The application flow and workflow section of the design document are used during the testing phase to ensure that the product works as intended.
- Requirements specifications. The requirements specifications are used to ensure that the product meets all of its functional and quality requirements.
The next step, identify the tools, involves tools that will be used to test the system and track the results. Standard tools, such as word processing software, presentation and spreadsheet tools, and the specialized tools shown below, can be used in the testing phase.
- Testing tools. Testing tools are used to test the system. They are specific to the types of environments, programs, and testing to be performed on them. For example, Web-based environments need Web-based testing tools, such as a Web browser.
- Bug tracking databases. These tools identify, categorize, log, and track the resolution of bugs. For example, a spreadsheet with a description of the problem, a rating, a potential solution, and the date and signature of the person reporting the bug is a type of bug tracking database.
- Source code control systems. These tools help when different people are working on units of the code at the same time. This helps to avoid overwriting or undoing changes of others. For example, implementing versions of the product and assigning version control to one person at a time is a type of control system.
The third step of the testing phase is to conduct the key activities shown below.
Design the testing approach. The purpose of this activity is to prepare for the testing that takes place. First you need to determine the level of testing and then the types of testing.
- Create the test plan. This activity involves creating a test plan that includes the specific testing to be performed, the testing approach, the test conditions, the test schedule, the expected results, and the personnel involved.
- Create the test model. This activity involves creating a system test model to represent a production environment and includes all databases and files. It is used to fully test every system modification.
- Perform the integration and user acceptance testing. The integration test verifies the accuracy of the communication among all programs in the new system. The user acceptance test simulates the actual working conditions of the new system, including the user manuals and procedures.
- Check the detailed results. This activity involves the PM and the team members checking the test results of each cycle to verify the proper performance of each function under normal and abnormal conditions.
The next step in the testing phase, obtain the desired outputs, involves obtaining the test results, which are used as evidence that all the planned cycles have run successfully and that all outstanding issues have been resolved.
4. Meet the milestones to complete this phase.
In the final step, the PM obtains a conversion readiness sign-off form from the stakeholders of the project. This is the milestone that needs to be met for this phase of the project.
The testing phase ensures that the product meets all requirements and increases the chances of a successful project. Once it is completed, the project can move on to the final phase of the IT project life cycle—the rollout phase.
The Construction Phase of an IT Project
The construction phase of an IT project involves building the application using the agreed-upon environment and specialized tools. Developers create the application by using the design document as their guide.
During the construction phase, the project manager (PM) doesn't actually take part in conducting the components, but must have an understanding of each, so that he or she can oversee the project in a monitoring role. The components of the construction phase of the IT project life cycle are described below.
1. Inputs
The only input needed for the construction phase is the design document created during the design phase of the life cycle. The design document input is used as an outline for the development team to follow. It identifies what the final product should do, how it should function, and any necessary technical details.
2. Key activities
The key activities for the construction phase are preparing the detailed design and performing the programming. To complete the first key activity, which is to prepare the detailed design for each work unit, you should use the technical design as your guide. The steps for completing the detailed design are listed below.
The primary tools needed to conduct the construction phase of the IT project life cycle are the specific programming languages and compilers that the programmers will use to create and test the programming code.
4. Outputs
The outputs of the construction phase of the IT project life cycle are the code, programming work units, test database, and unit/string test results. Once the outputs of the construction phase are complete, you will have a working application that can be tested during the next phase of the IT project life cycle. More information about the outputs is provided below.
The final component of the construction phase for the IT project life cycle, the milestones, must be met before the project can move on to the next phase of the life cycle. The milestones that must be reached during the construction phase of the IT project life cycle are the code review complete form and the string test sign-off.
During the construction phase, the project manager (PM) doesn't actually take part in conducting the components, but must have an understanding of each, so that he or she can oversee the project in a monitoring role. The components of the construction phase of the IT project life cycle are described below.
1. Inputs
The only input needed for the construction phase is the design document created during the design phase of the life cycle. The design document input is used as an outline for the development team to follow. It identifies what the final product should do, how it should function, and any necessary technical details.
2. Key activities
The key activities for the construction phase are preparing the detailed design and performing the programming. To complete the first key activity, which is to prepare the detailed design for each work unit, you should use the technical design as your guide. The steps for completing the detailed design are listed below.
- Complete the technical design. Complete any outstanding design work and estimate the impact of any design changes.
- Design the work units. Review the technical design and plan the individual work units for the application. A work unit is a logical portion of the project that can be designed and developed independently from another part of the project and then integrated as needed later.
- Complete the database design. Document the logical data structures and data areas used in each programming work unit and make this documentation available to the project's programmers.
- Review the performance design. The complete project team, along with end users, conduct a review of the programming work unit design to ensure that the design meets functional and quality requirements. This review helps ensure that the programmers understand the requirements and that the design is feasible.
- Iterate the detail design. After the design review, the preceding steps are conducted as many times as necessary to enable the project team to refine the design.
- Prepare the common test data. Construct a master test database with which to test each work unit. The database may contain the testing methods, test data, expected results, user instructions, and possible sample documents for use in the testing.
The primary tools needed to conduct the construction phase of the IT project life cycle are the specific programming languages and compilers that the programmers will use to create and test the programming code.
4. Outputs
The outputs of the construction phase of the IT project life cycle are the code, programming work units, test database, and unit/string test results. Once the outputs of the construction phase are complete, you will have a working application that can be tested during the next phase of the IT project life cycle. More information about the outputs is provided below.
- Code. Using a programming language, programmers write a sequence of instructions that translates the product design into a language that a computer can understand. The instructions are referred to as the program source code or the executable code.
- Programming work units. Programming work units are an output of the detailed design key activity and are used as the basis for the development of the code.
- Test database. A set of common test data is developed to provide quality control for unit testing.
- Unit/string test results. The actual test results from unit tests—and if applicable, string tests—need to be documented and preserved as part of the project documentation.
The final component of the construction phase for the IT project life cycle, the milestones, must be met before the project can move on to the next phase of the life cycle. The milestones that must be reached during the construction phase of the IT project life cycle are the code review complete form and the string test sign-off.
- Code review complete. Once the review of the code developed during the construction phase is complete, the PM can sign off the code review complete milestone.
- String text sign-off. The PM signs the string test sign-off to indicate acceptance of the string test results and implies the completion of unit testing.
Tuesday, July 3, 2007
The Design Phase of an IT Project
The purpose of the design phase of an IT project life cycle is to plan out a system that meets the requirements defined in the analysis phase. In the design phase, the project team defines the means of implementing the project solution—how the product will be created. To do this, the project team uses the inputs and tools to conduct the key activities, create the outputs, and meet the milestones for this phase.
The purpose of the design phase is to provide the project team with a means for assessing the quality of the solution before it has been implemented, when changes are still easy to make and are less costly. This phase includes the following elements.
1. Review the end user interface design.
Before the project manager can conduct the first key activity, the designer uses the project's storyboards to create the end user interface in terms of appearance, layout, and interaction techniques as seen by the end users.
The PM evaluates the design to ensure that it meets the users' needs and the corporate standards. The PM then meets with the designer and explains what's wrong and what's missing from the proposed design. If the PM is not satisfied with the design, the designer applies the necessary corrections, and the PM reviews it again.
When a PM looks at a design, he or she compares it to the inputs listed below. This evaluation is important because the developer will not be able to properly test the completed product during the testing phase if the design doesn't meet these requirements. If testing can't be conducted properly, the product can't move into the rollout phase.
Although PMs do not conduct the last two key activities of the design phase, it is important that they understand each activity. The designer and technical architect conduct the technical design activity to decide how they will implement the project design. By using the requirements specifications input as a guide, they create a document that includes the sections listed below. The technical design is then given to the PM to serve as the blueprint for the project.
Framework. The framework is a design that can be reused on a software development project. For example, the text entry field used on a user interface framework can be reused in a database design.
As in the technical design activity, the project manager does not actually have a part in conducting the final key activity of the design phase, except to receive a sign-off form. During quality verification and validation, end users and technical personnel verify and validate that the proposed design meets the user and quality requirements.
Upon completion of the review, an approval form is given to the project manager, indicating approval of the completed system design. This sign-off then becomes one of the milestones for the design phase.
Remember, it's easier and less costly to make changes in the design phase, before you implement the actual solution for the project. Take your time and design it right!
The purpose of the design phase is to provide the project team with a means for assessing the quality of the solution before it has been implemented, when changes are still easy to make and are less costly. This phase includes the following elements.
- The inputs required for this phase are the corporate standards, business process prototype, and requirements analysis.
- Only standardized tools found in all offices, such as word processing software, spreadsheets, and presentation software, are used in the design phase.
- The key activities for the design phase are to review the end user interface design, create the technical design, and perform the quality verification and validation.
- The single output for the design phase is the design document.
- The milestones for the design phase are the architecture assessment deliverable, design sign-off, and lifecycle assessment complete deliverable.
1. Review the end user interface design.
Before the project manager can conduct the first key activity, the designer uses the project's storyboards to create the end user interface in terms of appearance, layout, and interaction techniques as seen by the end users.
The PM evaluates the design to ensure that it meets the users' needs and the corporate standards. The PM then meets with the designer and explains what's wrong and what's missing from the proposed design. If the PM is not satisfied with the design, the designer applies the necessary corrections, and the PM reviews it again.
When a PM looks at a design, he or she compares it to the inputs listed below. This evaluation is important because the developer will not be able to properly test the completed product during the testing phase if the design doesn't meet these requirements. If testing can't be conducted properly, the product can't move into the rollout phase.
- User needs. Does the design include each of the user requirements? Are each of the user requirements correctly incorporated into the design?
- Corporate standards. Does the design include all the standards that specify products or technologies that the development team will use? Are the standards properly implemented in the design?
Although PMs do not conduct the last two key activities of the design phase, it is important that they understand each activity. The designer and technical architect conduct the technical design activity to decide how they will implement the project design. By using the requirements specifications input as a guide, they create a document that includes the sections listed below. The technical design is then given to the PM to serve as the blueprint for the project.
Framework. The framework is a design that can be reused on a software development project. For example, the text entry field used on a user interface framework can be reused in a database design.
- Coding standards. Programmers have to follow these rules to ensure consistency in the programming code since usually more than one programmer will work on a project. A sample coding standard might read, "Do not use capital letters for file names when coding."
- Task breakdown. Development is divided into tasks created separately and then integrated into a final product. Task breakdown makes it easier for a PM to assign work during the construction phase. For example, three tasks might be the user interface, the database, and the help feature.
- Project timeline. A timeline for completion is estimated for each task required to complete the project. For example, it will take four days to create the user interface, three days for the database, and two and a half days for the help feature, for a total of nine and a half days.
As in the technical design activity, the project manager does not actually have a part in conducting the final key activity of the design phase, except to receive a sign-off form. During quality verification and validation, end users and technical personnel verify and validate that the proposed design meets the user and quality requirements.
Upon completion of the review, an approval form is given to the project manager, indicating approval of the completed system design. This sign-off then becomes one of the milestones for the design phase.
Remember, it's easier and less costly to make changes in the design phase, before you implement the actual solution for the project. Take your time and design it right!
Topics:
architecture,
design,
interface,
phase,
stage
Key Activities of the Project Analysis Phase
The analysis phase of the IT project life cycle produces the detailed requirements and system architecture specifications for a project. Most importantly, it establishes what the end user wants the system to do.
During this phase, models of the application are developed. The development team uses these models to ensure that it understands the system requirements during the design phase and that the project meets the client's expectations.
In order to produce the detailed requirements of the analysis phase, the project manager (PM) must be familiar with the components listed below. Remember, the inputs and tools are used to create the key activities, which are the focus of this topic. Those key activities are then used to produce the outputs to meet the milestone for this phase.
1. Identify the end user requirements.
The first key activity, identify the end user requirements, describes user needs in terms of the new system and the differences between the new and the old system. Determining the end user requirements involves the two steps shown below.
The next key activity in the analysis phase is to identify the quality requirements, which will help you understand how well the system will carry out its functions. To identify the quality requirements, review user requirements and product and project guidelines from the information plan. Explanations of what a quality requirement should contain are shown below.
The next key activity is to conduct the requirements analysis. This is the process of increasing the team's understanding of the system requirements and translating them into a system design. The two models listed below are created during this key activity.
During this phase, models of the application are developed. The development team uses these models to ensure that it understands the system requirements during the design phase and that the project meets the client's expectations.
In order to produce the detailed requirements of the analysis phase, the project manager (PM) must be familiar with the components listed below. Remember, the inputs and tools are used to create the key activities, which are the focus of this topic. Those key activities are then used to produce the outputs to meet the milestone for this phase.
- The inputs required for this phase are the conceptual design, current system description, information plan, and project plan.
- The tools needed for this phase are word processing software, presentation software, spreadsheets, and process and event modeling software.
- The key activities for this phase are the end user requirements, quality requirements, and requirements analysis.
- The outputs of this phase are the business process prototype and the requirements analysis.
- The only milestone for this phase is the requirements' sign-off.
1. Identify the end user requirements.
The first key activity, identify the end user requirements, describes user needs in terms of the new system and the differences between the new and the old system. Determining the end user requirements involves the two steps shown below.
- Identify user requirements. The PM uses both the conceptual design inputs and the needs analysis section of the information plan to understand what the new system must do to satisfy the users' needs. The PM then prepares a statement that indicates what the users will be able to do with the product.
- Perform a gap analysis. After the PM has identified the user requirements, the next step is to review the current system documentation and then perform a gap analysis, which determines the differences between the current and the new system and identifies the changes required.
The next key activity in the analysis phase is to identify the quality requirements, which will help you understand how well the system will carry out its functions. To identify the quality requirements, review user requirements and product and project guidelines from the information plan. Explanations of what a quality requirement should contain are shown below.
- Individual testable requirements. Quality requirements shouldn't be bunched together in a paragraph. Each requirement should have a separate entry that fully describes it. The description should be clear and understandable.
- An explanation of how requirements will be tested. Explain exactly how the developers will test the function to determine whether each requirement is properly implemented. The developers can use inspection or demonstration, for example.
- Prioritization. It's important that each requirement be prioritized in order of importance. Most PMs use the following scale: "High" indicates that the requirement must be included, "medium" indicates that it is necessary but can be added later, and "low" indicates that it is nice to have but not absolutely necessary.
The next key activity is to conduct the requirements analysis. This is the process of increasing the team's understanding of the system requirements and translating them into a system design. The two models listed below are created during this key activity.
- Process model. Process modeling is a technique for understanding, defining, and precisely representing the processes involved in developing an application. During process modeling, the PM uses modeling software to draw diagrams of each process. The diagrams are then used to develop the application.
- Event model. Event modeling is a process that enables the project team to understand the events that trigger a process, which in turn causes a number of results. During event modeling, the PM uses modeling software to draw diagrams of each event and their possible results.
Topics:
activities,
analysis,
phase
Sunday, July 1, 2007
Project Planning Phase Outputs and Milestones
Did you know that the planning phase of an IT project can make or break that project? If not conducted properly, the planning phase can cause a domino effect on the other life cycle phases and eventually cause the project to fail. This is why successful project managers spend so much time on this phase.
The majority of the project manager's work during the planning phase involves the completion of three key activities—project initiation and organization, project definition and planning, and management review and approval. However, the project manager's job does not end there. The key activities are then used to obtain the outputs, and the outputs are used to meet the milestone, thus completing this cycle of the project.
Once the members of the project team have concluded all of the key activities of the planning phase, they will have the outputs listed below. These outputs will become the inputs to the analysis phase of the project life cycle.
The project plan sign-off is the milestone that must be met during the planning phase. It indicates that the planning phase of the IT project life cycle has been completed. The project can now move on to the analysis phase.
Remember, in order to move onto the analysis phase and proceed with your project, you must first develop the outputs of the planning phase and obtain the sign-off form from management, which is the milestone for this phase of the project.
The majority of the project manager's work during the planning phase involves the completion of three key activities—project initiation and organization, project definition and planning, and management review and approval. However, the project manager's job does not end there. The key activities are then used to obtain the outputs, and the outputs are used to meet the milestone, thus completing this cycle of the project.
Once the members of the project team have concluded all of the key activities of the planning phase, they will have the outputs listed below. These outputs will become the inputs to the analysis phase of the project life cycle.
- The business case. A business case is a request for project investment. It is a high-level description of the project's information systems and related business objectives.
- The conceptual design. The conceptual design can be a rough drawing, a flowchart, or storyboards that show the general shape and location of all design elements for the proposed application.
- The project plan. The project plan is used to guide project execution and control. It includes an overview of the project, a description of how the project is organized, details about the management and technical processes to be used, and a description of the work to be done, as well as a schedule and budget information.
The project plan sign-off is the milestone that must be met during the planning phase. It indicates that the planning phase of the IT project life cycle has been completed. The project can now move on to the analysis phase.
Remember, in order to move onto the analysis phase and proceed with your project, you must first develop the outputs of the planning phase and obtain the sign-off form from management, which is the milestone for this phase of the project.
Topics:
business case,
conceptual,
milestone,
phase,
plan
Wednesday, June 27, 2007
Incorporating IT Project Deliverables
Your promise to complete a project by a particular date has fallen through. As you think back, you realize that you had no way of knowing whether or not things were progressing smoothly.
How can you ensure that you have a check process in place for your next IT project? One suggestion is to incorporate project deliverables.
Project deliverables are the final product or result of a particular phase of a project. Deliverables are ultimately passed on to another party, either professionals who will use the deliverable to begin the next phase of the project, or the customer if it is part of the final product.
When planning a project, IT professionals establish specific types of project deliverables to help determine when a stage in the process is complete. These deliverables also can help you identify whether a problem exists early in the process.
There is no limit to the number of deliverables you can incorporate into each phase of your project. The following are a few examples of the most common deliverables.
1. Organization charts. Organization charts show the breakdown of the responsibilities or duties of the individuals in each unit. These charts can include information about the sponsoring company, the customer's company if external, and the authority, responsibilities, and communication breakdown for a project.
An example of an organization chart is the organizational breakdown structure. Your company's OBS chart may include the name of the employee performing each of the roles identified on the chart.
2. Work packages. Work packages are comprised of a number of precise working documents that provide details on specific business tasks of the project. An example of this deliverable is the Statement of Work (SOW).
3. Planning documents. Planning documents are used to develop and maintain a feasible method for addressing the business needs of the project. The amount and detail of the information contained in these documents depend on the size of the project.
Work schedules and cost estimates are examples of this deliverable. Work schedules can help you determine the staff numbers and skill sets needed for the project. Cost estimates give you an approximation of the total project cost.
Remember, by incorporating deliverables into the project phases, you and you team can more effectively plan and manage your next IT project.
How can you ensure that you have a check process in place for your next IT project? One suggestion is to incorporate project deliverables.
Project deliverables are the final product or result of a particular phase of a project. Deliverables are ultimately passed on to another party, either professionals who will use the deliverable to begin the next phase of the project, or the customer if it is part of the final product.
When planning a project, IT professionals establish specific types of project deliverables to help determine when a stage in the process is complete. These deliverables also can help you identify whether a problem exists early in the process.
There is no limit to the number of deliverables you can incorporate into each phase of your project. The following are a few examples of the most common deliverables.
1. Organization charts. Organization charts show the breakdown of the responsibilities or duties of the individuals in each unit. These charts can include information about the sponsoring company, the customer's company if external, and the authority, responsibilities, and communication breakdown for a project.
An example of an organization chart is the organizational breakdown structure. Your company's OBS chart may include the name of the employee performing each of the roles identified on the chart.
2. Work packages. Work packages are comprised of a number of precise working documents that provide details on specific business tasks of the project. An example of this deliverable is the Statement of Work (SOW).
3. Planning documents. Planning documents are used to develop and maintain a feasible method for addressing the business needs of the project. The amount and detail of the information contained in these documents depend on the size of the project.
Work schedules and cost estimates are examples of this deliverable. Work schedules can help you determine the staff numbers and skill sets needed for the project. Cost estimates give you an approximation of the total project cost.
Remember, by incorporating deliverables into the project phases, you and you team can more effectively plan and manage your next IT project.
Tuesday, June 26, 2007
Outputs to the IT Project Phases
Think back to the last time you were in a bakery where the aroma of freshly baked bread teased your senses. Making bread may be less complicated than administering an IT project, but it follows a similar development process with inputs (ingredients), tools (oven), and outputs (a loaf of bread).
Using a recipe and the necessary tools, the baker expects outputs at each stage—a ball of dough made from various ingredients, a larger ball of raised dough, and finally a perfectly formed and delicious loaf of bread.
An IT project also produces outputs, which are known as deliverables. These outputs are the results derived from each of the IT project's six phases—planning, analysis, design, construction, testing, and rollout.
Outputs, or deliverables, can help your team keep a project on track. Well-planned outputs are also an effective way for managers, IT organizations, sponsors, and users to learn effective lessons from a project. Remember to focus on achieving benefits and objectives when determining the outputs that will be generated during each phase of your project.
There are a number of major outputs for each phase in an IT project. Not all phases have the same number of outputs, but all deliverables help you and your team achieve success with the end product. Examples of outputs for each of the six IT project phases are listed below.
Planning phase. An example of a planning phase output is the business case, which provides validation for any project decisions made. It acts as the framework for performing all evaluations and as the starting point for guiding the management of the project.
Analysis phase. An example of an analysis phase output is the requirements specification, which contains or refers to the definition and details about the data, event, and process models, as well as the project quality requirements.
Design phase. An example of a design phase output is the design document, which contains or refers to the application architecture and flows, database and user interface designs, and the workflow diagram.
Construction phase. An example of a construction phase output is a programming work unit. Programming work units lay the base for the development of project codes for testing aids and application and conversion programs. Other nonprocedural codes are also included when applicable.
Testing phase. An example of a testing phase output is the operating instructions, which can be in the form of manuals, installation procedures, or instructions for using the new system. These instructions would be accessible to all end users.
Rollout phase. An example of a rollout phase output is the post-conversion review document, which can contain specifics on the scope of the conversion process and details about any problems that have occurred during conversion.
It is important to be aware of the outputs for each phase of your project. As you move through each phase, you will begin to understand the relevance of the role of each output for the particular phase to which it belongs.
Outputs can help your team tremendously by providing direction and valuable methods of recording the processes followed throughout your project.
Using a recipe and the necessary tools, the baker expects outputs at each stage—a ball of dough made from various ingredients, a larger ball of raised dough, and finally a perfectly formed and delicious loaf of bread.
An IT project also produces outputs, which are known as deliverables. These outputs are the results derived from each of the IT project's six phases—planning, analysis, design, construction, testing, and rollout.
Outputs, or deliverables, can help your team keep a project on track. Well-planned outputs are also an effective way for managers, IT organizations, sponsors, and users to learn effective lessons from a project. Remember to focus on achieving benefits and objectives when determining the outputs that will be generated during each phase of your project.
There are a number of major outputs for each phase in an IT project. Not all phases have the same number of outputs, but all deliverables help you and your team achieve success with the end product. Examples of outputs for each of the six IT project phases are listed below.
Planning phase. An example of a planning phase output is the business case, which provides validation for any project decisions made. It acts as the framework for performing all evaluations and as the starting point for guiding the management of the project.
Analysis phase. An example of an analysis phase output is the requirements specification, which contains or refers to the definition and details about the data, event, and process models, as well as the project quality requirements.
Design phase. An example of a design phase output is the design document, which contains or refers to the application architecture and flows, database and user interface designs, and the workflow diagram.
Construction phase. An example of a construction phase output is a programming work unit. Programming work units lay the base for the development of project codes for testing aids and application and conversion programs. Other nonprocedural codes are also included when applicable.
Testing phase. An example of a testing phase output is the operating instructions, which can be in the form of manuals, installation procedures, or instructions for using the new system. These instructions would be accessible to all end users.
Rollout phase. An example of a rollout phase output is the post-conversion review document, which can contain specifics on the scope of the conversion process and details about any problems that have occurred during conversion.
It is important to be aware of the outputs for each phase of your project. As you move through each phase, you will begin to understand the relevance of the role of each output for the particular phase to which it belongs.
Outputs can help your team tremendously by providing direction and valuable methods of recording the processes followed throughout your project.
Inputs to the IT Project Phases
Have you ever heard the term "garbage in, garbage out (GIGO)"? This is a term used to describe the results you would receive if you entered insufficient or incorrect data into a computer, for example. It also applies to your IT project.
You should ensure that all of the information you use in your project is of good quality. Any project can be detrimentally affected by the use of poorly researched information.
With thorough planning, you will be better able to determine and gather the information you will need for your IT project. By documenting this information, you will have a road map for developing an effective IT project plan.
In project management, the documents or documentable items that are produced and will be acted upon are called "inputs." These documents contain all the information your team has researched to make the project run smoothly and efficiently.
There are a number of inputs to consider for each phase of an IT project. Not all phases have the same number of inputs, but all inputs are beneficial to the success of the end product. Examples of inputs for each of the six IT project phases are listed below.
Planning phase. An example of a planning phase input is the information plan, which contains an extensive description of the company's present systems and the objective of the project.
Analysis phase. An example of an analysis phase input is the conceptual design, which describes the scope, architecture, and other aspects of the new system in detail.
Design phase. An example of a design phase input is the business process prototype, which depicts the working functions of the new system or product. It also highlights crucial or problematic areas.
Construction phase. An example of a construction phase input is the design document. The design document of the construction phase can include references or details on application flow, database design, and a workflow design.
Testing phase. An example of a testing phase input is user documentation. This documentation includes user instructions and procedures that the end users will require. It also is appropriate to test the user documentation during this phase. This will help uncover and eliminate documentation errors that could result in the delivery of inappropriate instructions to the end user.
Rollout phase. An example of a rollout phase input is the current systems description. When designing a new system, it is necessary to document any changes that must be made to the old system to accommodate the new structure. These details are included in the current systems description.
By being familiar with the inputs of each phase of an IT project, you and your team can be more confident that you have given adequate consideration to all required tasks in the development of your new system or product.
You should ensure that all of the information you use in your project is of good quality. Any project can be detrimentally affected by the use of poorly researched information.
With thorough planning, you will be better able to determine and gather the information you will need for your IT project. By documenting this information, you will have a road map for developing an effective IT project plan.
In project management, the documents or documentable items that are produced and will be acted upon are called "inputs." These documents contain all the information your team has researched to make the project run smoothly and efficiently.
There are a number of inputs to consider for each phase of an IT project. Not all phases have the same number of inputs, but all inputs are beneficial to the success of the end product. Examples of inputs for each of the six IT project phases are listed below.
Planning phase. An example of a planning phase input is the information plan, which contains an extensive description of the company's present systems and the objective of the project.
Analysis phase. An example of an analysis phase input is the conceptual design, which describes the scope, architecture, and other aspects of the new system in detail.
Design phase. An example of a design phase input is the business process prototype, which depicts the working functions of the new system or product. It also highlights crucial or problematic areas.
Construction phase. An example of a construction phase input is the design document. The design document of the construction phase can include references or details on application flow, database design, and a workflow design.
Testing phase. An example of a testing phase input is user documentation. This documentation includes user instructions and procedures that the end users will require. It also is appropriate to test the user documentation during this phase. This will help uncover and eliminate documentation errors that could result in the delivery of inappropriate instructions to the end user.
Rollout phase. An example of a rollout phase input is the current systems description. When designing a new system, it is necessary to document any changes that must be made to the old system to accommodate the new structure. These details are included in the current systems description.
By being familiar with the inputs of each phase of an IT project, you and your team can be more confident that you have given adequate consideration to all required tasks in the development of your new system or product.
Monday, June 25, 2007
The Six Phases of an IT Project
Have you ever heard the saying "putting the cart ahead of the horse?" If you wanted to move your cart forward, having the cart in front would not really help. In order to make progress, you would want to put the horse ahead of the cart.
Performing tasks in sequence is also an important aspect of IT projects. The phases of an IT project, also known as a software development lifecycle, make up the framework of an IT project. These phases, which are listed below in sequence, will help you to address the business needs of your project, and better define the activities that will occur throughout the project's entire life span.
1. Planning
First, you must look at the information technology needs of your company. These needs are determined during the planning phase of an IT project by using an information-gathering technique such as a questionnaire.
Keep in mind that the objective must address and remedy an issue or a problem within the company. Once you define the objective, you can put an action plan into place. A description of the development approach that the IT team will take and the estimation of the overall cost are factors that are determined during this phase.
2. Analysis
The analysis phase is the second phase in the software development lifecycle. This phase focuses on the functions the end system will need to perform.
Once you establish the performance needs, you will be able to develop and formalize a more detailed description of the system. The use of business, data, event, and process models during the analysis phase will ensure that both the development team and the end user are on the same track.
3. Design
The third phase of an IT project is the design phase. In it, the plan for the end system is developed. This plan should accurately define the implementation of the project without actually executing the project.
4. Construction
During the fourth phase of the project, the IT team actually constructs the project or system. In this construction phase, the team uses a process map that identifies the procedures that need to be completed to duplicate the agreed-upon plan.
5. Testing
The testing phase is possibly the most critical of all the IT project phases. It is in this phase that the team determines which tests to implement to ensure that the system being produced will be of the highest quality.
6. Rollout
The final phase in an IT project is rollout. It is during this phase that the team begins the activities for releasing the finished product to the end user. Planning for the rollout activities can help the process progress more smoothly.
For example, if another system is already in place, your team will need to thoroughly review the conversion process to ensure the smooth transition from the previous system to the new one.
Every organization should have a structure in place to deal with processes, principles, and guidelines for every IT project. The phases described above can provide a useful framework for the effective development and completion of your next IT project.
Performing tasks in sequence is also an important aspect of IT projects. The phases of an IT project, also known as a software development lifecycle, make up the framework of an IT project. These phases, which are listed below in sequence, will help you to address the business needs of your project, and better define the activities that will occur throughout the project's entire life span.
1. Planning
First, you must look at the information technology needs of your company. These needs are determined during the planning phase of an IT project by using an information-gathering technique such as a questionnaire.
Keep in mind that the objective must address and remedy an issue or a problem within the company. Once you define the objective, you can put an action plan into place. A description of the development approach that the IT team will take and the estimation of the overall cost are factors that are determined during this phase.
2. Analysis
The analysis phase is the second phase in the software development lifecycle. This phase focuses on the functions the end system will need to perform.
Once you establish the performance needs, you will be able to develop and formalize a more detailed description of the system. The use of business, data, event, and process models during the analysis phase will ensure that both the development team and the end user are on the same track.
3. Design
The third phase of an IT project is the design phase. In it, the plan for the end system is developed. This plan should accurately define the implementation of the project without actually executing the project.
4. Construction
During the fourth phase of the project, the IT team actually constructs the project or system. In this construction phase, the team uses a process map that identifies the procedures that need to be completed to duplicate the agreed-upon plan.
5. Testing
The testing phase is possibly the most critical of all the IT project phases. It is in this phase that the team determines which tests to implement to ensure that the system being produced will be of the highest quality.
6. Rollout
The final phase in an IT project is rollout. It is during this phase that the team begins the activities for releasing the finished product to the end user. Planning for the rollout activities can help the process progress more smoothly.
For example, if another system is already in place, your team will need to thoroughly review the conversion process to ensure the smooth transition from the previous system to the new one.
Every organization should have a structure in place to deal with processes, principles, and guidelines for every IT project. The phases described above can provide a useful framework for the effective development and completion of your next IT project.
Subscribe to:
Posts (Atom)