Project Monitoring & Control Techniques
Project Management Concept:
It is an art and science of planning and leading software projects.
Project Management-> software project- planned, implemented, Monitored, controlled.
Effective software project management focuses on the four P’s:
The People: It deals with the cultivation of motivated, highly skilled people.
Software engineering institute has developed a people management capability maturity model (PM-CMM) to enhance the readiness of thesoftware organizations to undertake increasingly Complex Applications by helping to the talented needed to improve their software development capability.
The People management maturity model focuses on
People consists of
The People: The Stakeholder:
There are mainly 5 categories of stakeholder:
- Senior Manager: Define business issues that often have significant influence on the project.
- Project (Technical) Managers: They “Plan, Motivate, Organised, and Control”the practitioners who do the work.
- Practitioner: They deliver the technical skills that are necessary to engineer a product or application.
- Customers: Specify the requirement for the software to be engineered and other stakeholders who have a peripheral interest in the outcome.
- End users: Interact with the software once it is released for production use.
The people: Team leaders
Team Leader Qualities:
• Motivational- the ability to encourage technical people to produce to their best ability.
- Organisation-the ability to mold existing processes.
- Ideas or innovations-ability to encourage to go beyond their skills.
Another set of useful leadership Traits:
- – problem solving:Diagnose, structure a solution, apply lessons learned, remain flexible.
- – Managerial Identity: Take charge of the project, have confidence to assume control, have a assurance to allow good people to do their jobs.
- -Achievement :Reward initiative, demonstrate that control risk taking will not be punished.
- -Influence and team building:Be able to ‘ read’ people, understand verbal and nonverbal signals. Able to react to the signals, remain under control in high- stress situations.
The people: The software team
Seven project factors to be considered when selecting a software development team.
Four Organizational paradigm for Software Development Teams :
- 1. Closed paradigm:Traditional hierarchy of authority works well when producing software similar to past efforts, members are less likely to be innovative .
- 2. Random paradigm: Depends on individual initiative of team members , work well for project requiring innovation technological break.
- 3. Open paradigm: hybrid of the closed and random paradigm, works well for solving Complex problems, requiring collaboration, communication, and censensus among members.
- synchronous paradigm:Organizes team members based on the network pieces of the problem, members have little communication outside of their subgroups.
Project Management Concept
The scope of the software development must be established and bounded:
- Context: How does the software to the built fit into a larger system, product, or business context and what constraint are imposed as a result of the context?
- Information Objective– what customer visible data objects are produced as output from the software? What data object are required for input?
- Function and performance:What function does the software performance to transform input data into output? Are there any special performance characteristics to be addressed.
Software Project scope must be unambiguous and understand at both the “Managerial and Technical levels”.
The project manager must decide process model is most appropriate based on
The customer who have requested the product and the people who will do the work.
The characteristics of the product itself
The project environment in which the software team works <
The Project :
Planning and controlling a software project is done for one the primary reason. It is the only known way to manage complexity.
A series of questions that like to add definition of the key project characteristic and resultant project plan.
- – why is the system being developed?
Assesses the validity of business reason and justifications.
- – what will be done?
Establishing the task set required for the project.
- -When will be done –
Establishes a project schedule.
- -Where are they organizationally located?
->Notes the organisational location of the team members, customers and other stakeholder.
- -Who is responsible for functional-
defines the role and responsibility of each member.
- – How will the job is done technically and managerially?
-> establishes the management and Technical strategy for the project.
- – how: much of each resources is needed?
-> Establishes estimates based on the answer to the previous questions.