Create A Plan For An Information Systems Project

Create A Plan For An Information Systems Project

Create a plan for an information systems project. For the final project you will be synthesizing the information from the text and your learning throughout the term. You will create a project plan using MS Project that integrates several aspects of project management, including: project scope management, project time management, project cost management, and project human resource management. You are free to develop any information systems project for the final. Note that an information systems project is focused on developing a software system or application and follows an SDLC model. The project you choose has the following constraints:

1. Budget – a minimum of $50,000 and no more than $200,000.

2. Timeline – minimum of 8 weeks and no more than 52 weeks.

3. Resources – a minimum of five named resources.

Your project plan will have the following major activities (Level 1 of the WBS):

1. Initiating

2. Planning

3. Executing

4. Controlling

5. Closing

These activities provide the structure for your Work Breakdown Structure (WBS). Under each activity, add tasks relevant to your project. For planning, be sure to address collecting requirements. Since your project focuses on creating an information system, most tasks will be in the Executing activity and must include at least:

- Analysis

- Design

- Implementation

- Testing

Add at least two appropriate subtasks under each of these phases. Your project plan must include the following elements:

1. WBS created as a task hierarchy (task names as shown in MS Project) — representing scope management.

2. Task duration and sequencing (when tasks start, their durations, and relationships) — representing time management.

3. Resources assigned to each task and associated costs (using the Resource Sheet to define resources and their costs) — representing human resource management.

4. Costs for each activity shown in the Gantt Chart (by adding the “cost” column to display costs based on assigned resources) — representing cost management planning.

5. At least one milestone for each Level 1 activity in the WBS (milestones have no duration).

6. Critical tasks on the critical path highlighted in red (let MS Project determine this automatically).

7. Assume approximately one quarter of the work has been completed at this point. Mark relevant tasks as complete or partial to reflect progress.

Paper For Above instruction

Creating a comprehensive project plan for an information systems project involves integrating all critical elements of project management. This process adheres to the structured phases of the Software Development Life Cycle (SDLC) and employs MS Project as a planning tool to visualize and manage the project effectively.

Defining the Project Scope and WBS Development

The initial step in planning involves defining the scope clearly through the WBS. The project scope should outline a software development initiative within the given constraints—a budget between $50,000 and $200,000, a timeline spanning from 8 to 52 weeks, and at least five named resources involved. The WBS is structured into five Level 1 activities: Initiating, Planning, Executing, Controlling, and Closing. These activities form the backbone of the project and establish a hierarchical task framework, capturing scope management and task dependencies.

Within each activity, detailed tasks are added. For instance, under ‘Planning,’ tasks such as requirements gathering, resource planning, and risk assessment are included. The ‘Executing’ phase is subdivided into analysis, design, implementation, and testing, each having at least two subtasks. These might include requirements analysis, system architecture design, coding, unit testing, integration testing, and user acceptance testing, facilitating detailed scheduling and resource allocation.

Time Management: Sequencing and Duration

Proper sequencing of tasks is vital for maintaining a realistic timeline. In MS Project, dependencies (finish-to-start, start-to-start, etc.) are established to illustrate task relationships clearly. Durations are assigned based on the complexity of each task, with milestones marking the completion of major activities such as requirements definition, system design, and testing sign-offs. MS Project’s critical path analysis highlights the sequence of tasks that directly impact the project’s finish date, highlighting vital activities that need focused management.

Resource Allocation and Cost Management

Assigning resources to tasks involves selecting personnel and tools from the Resource Sheet, with each resource assigned a specific cost rate. These costs are linked to tasks so that MS Project can automatically calculate the expense associated with each activity. This integration supports cost management planning, enabling project managers to monitor expenses against the allocated budget continually. Resources should be diverse, including project managers, analysts, developers, testers, and technical support staff, to reflect realistic project scenarios.

Progress Tracking and Critical Path Analysis

Assuming that approximately 25% of the work has been completed, tasks in the initial phases should be marked accordingly. For example, project initiation might be fully complete, while early planning or analysis phases may be partially done. MS Project allows marking tasks as 50% complete or fully complete, thus providing an ongoing visual representation of progress.

The software automatically identifies the critical path, highlighting unaccomplished tasks that could delay project completion if delayed. Critical tasks are displayed in red, focusing attention on activities that require management intervention if slips occur.

Monitoring and Controlling

Regular monitoring through the Gantt Chart and task status updates are essential for project control. The ‘Controlling’ phase includes tracking schedule performance, managing scope changes, and updating resource allocations as needed. Cost monitoring ensures the project remains within budget parameters. Effective control requires understanding variances and facilitating corrective actions promptly.

Closing and Project Completion

The final phase involves closing all project activities, documentation, and handoffs. It marks the administrative closure and evaluation of project success relative to initial objectives, scope, timeline, and budget.

Conclusion

Developing a detailed project plan with MS Project provides clarity on scope, schedule, costs, and resources. It supports proactive management by highlighting critical tasks, tracking progress, and maintaining budget control. For an information systems project following SDLC, this structured approach facilitates successful delivery within constraints.

References

  • Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). PMI.
  • Schwalbe, K. (2018). Information Technology Project Management (9th Edition). Cengage Learning.
  • Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. Wiley.
  • Heldman, K. (2018). PMP Project Management Professional Study Guide. Wiley.
  • Meredith, J. R., & Mantel, S. J. (2017). Project Management: A Managerial Approach. Wiley.
  • PMI. (2021). The Standard for Program Management. Project Management Institute.
  • Svejvig, P., & Andersen, P. (2015). Rethinking project management: A structured literature review with a critical approach. International Journal of Project Management, 33(2), 284-303.
  • Chua, D. K. (2012). Managing project scope: Scope creep and project success. International Journal of Managing Projects in Business, 5(2), 278-287.
  • Leach, L. P. (1999). Critical Chain Project Management. Artech House.
  • Shenhar, A. J., & Dvir, D. (2007). Reinventing project management: The Diamond approach. Harvard Business Review, 85(4), 73-82.

Related Assignments