Activities in Software Project Management

Save

Software project management involves a project manager coordinating skills, techniques, data and resources in a way that allows a project to be complete before a given deadline that satisfies the expectations of those the project affects. Software project management involves meetings, interviews, organization and a firm command of effective communication between various department levels.

Scope

  • One of the first priorities in software project management is defining the full scope of the project. An analysis is done of what the end goal of the project is to be, how much budget will be given to the software project's completion and what departments will need to be involved. A plan is written detailing key players of the project, such as the project manager, his contact information, the approach that will be used to begin the project and the roles and key responsibilities of the software development team, network engineer and help desk staff. A tentative software deployment and maintenance schedule is also drawn up.

Time

  • During time management activities, the needs of the software creation and development are broken down into sections and divided among team members for completion. The tasks are to be completed by certain times, one step at a time, or are to be completed by a deadline with different teams working on separate tasks at the same time. Each software creation project is different. Staff numbers are reviewed, special skills sets analyzed and teams created based on strengths. For example, creating the software will involve integration and resource analysis, programming and creating the user interface, database reconciliation and functional programming. Each step of the project will be put against a time constraint with each section having its own deadline. These deadlines are also known as benchmarks.

Integration

  • Another team is put together specifically to discuss and analyze the full feasibility and benefit of completing the project. This team will interview end users who interact with the company's current software applications. Information technology employees who maintain the current company network will discuss any issues that may arise with the deployment of the new software, such as managing downtimes, and which method is best for testing.

Quality

  • Quality management takes place before, during and after the creation and deployment of the new software. Charts will be made and the software will be tested against business expectations, such as whether the software processes data and stores it correctly, or retrieves and displays correct information to the user. End users will provide feedback and comments about the user-friendliness of the software and any glitches they may experience. Quality assurance involves monitoring the financial costs of building the software, such as the hours put in by programmers, networking staff and the project management team. The project manager will measure the successfulness of the software creation project by analyzing final reports.

References

  • "Information Technology Project Management"; Kathy Scwalbe, Ph.D.; 2007
  • Photo Credit smart management image by araraadt from Fotolia.com
Promoted By Zergnet

Comments

You May Also Like

Related Searches

Check It Out

3 Day-to-Night Outfits for the Work Week

M
Is DIY in your DNA? Become part of our maker community.
Submit Your Work!