Project Assignment on Managing projects in Software



Project Assignment on Managing projects in Software

Work Activities plan

Main Requirements of the Project

To advertise and recruit required professionals.

To analyze and document the specifications for the required functionality.

To acquire the needed hardware and software as part of IT infrastructure facilities.

To design, implement, test and operate the entire system.

Next step is defining human resources in terms of category, seniority and hourly cost:

Functional expert(s) - Knows the business process

Technical support - Technical product knowledge

Workflow Business Analyst - Workflow tools expert

System Administrator- Maintain workflow environment

Business Analyst - assist in doing a business process analysis

The Number of Programmers and Designers Needed To Finish the Project

These days, the cost of the project is often fixed before the design is done, and sometimes even before design has begun. Estimation now becomes more of guesswork based upon experience that was gained by screwing up earlier estimates. Without the design, it was quite impossible to know how many lines of code/functions/components/objects would be required. The estimator should rely on data and documents available before one starts the design, such as the functional and non-functional requirements, workflows, and use-cases. Therefore, requirements gathering and analysis is very critical to the project's estimation (design, development, and testing).

Using these documents, the estimator may create an object hierarchy tree simultaneously. The object hierarchy tree can help identify different levels/types of objects to be created, what is expected from these objects, and even some attributes for the objects. Therefore, without having an application design in place, the scope of work to be done, in terms of functionality required, can be identified.

Schedule Inputs

You need several types of inputs for the company to create a project schedule:

Personal and project calendars - Understanding working days, shifts, and resource availability is critical to completing a project schedule.

Description of project scope - From this, you can determine key start and end dates, major assumptions behind the plan, and key constraints and restrictions. You can also include stakeholder expectations, which will often determine project milestones.

Project risks - You need to understand these to make sure there's enough extra time to deal with identified risks - and with unidentified risks (risks are identified with thorough Risk Analysis).

Lists of activities and resource requirements - Again, it's important to determine if there are other constraints to consider when developing the schedule. Understanding the resource capabilities and experience you have available - as well as company ...