SPPM notes.

1. Basics of Software Project Management: -  Software Engineering is defined as a systematic approach for development and maintenance. 


2. Agile process: -   (liveliness and responds to changes) "Agile is dynamic, content-specific, aggressively change embracing and growth oriented. An agile team is a nimble team that responds to changes. Changes occur in the software being built, team members, new technology and all kinds that have impact on the products. The agile team produces (or) develops a software that responds to changes with their skills and their ability to collaborate.


3. Five phases of unified process: -  Inception; Elaboration; Construction; Transition; Production.


4. Spiral model and concurrent model: - Spiral model is an evolutionary process model. It is a cyclic approach where each phase leads to the next. Concurrent model is an iterative and concurrent phase model. The activities are concurrent and different at each phase. It has a series of events that triggers the state from one to another.


5. Team Software Process (TSP): -  TSP is a collection of disciplined PSP members to produce a high quality timely software. The TSP is defined for a team which has at-least two members; have a common goal; each person is assigned a specific role; and the members are dependent on each other to develop the product.


6. Guidelines for communication: - Listen; Prepare for the communication; Facilitate the communication; Make face-to-face conversation; stay focused; If there is ambiguity draw a picture; Make ideas clear; If both parties win then its successful.


7. Wideband Delphi:- Wideband Delphi is an effort estimation method. It includes planning, kickoff- meeting, assembling task, and reviewing results. The coordinator is responsible for selecting the moderator and team numbers. The team consists of 3 to 7 members.


8. Unit Testing: - Unit Testing is the verification effort of the smallest unit of the software design- the software component or module. It uncovers errors within the boundary of the module. Unit testing focuses on the internal process logic and data structures of the modules.It can be done in parallel among the software modules.


9.  Work break down structure: - Work break down structure is the breaking down of the larger project into smaller chunks or sub-tasks.The project manager and the subject expert is responsible for splitting the project into sub-tasks. Two rules are present 1) two weeks rule. 2) 8/80 rule.


10. Bug tracking: - Bug tracking means keeping track of the reported software bugs. It is also called as defect tracking or issue tracking. The main component in bug tracking system is the database which contain facts about the bugs reported. The facts include time, severity and cause of the bugs and also the program behavior after the bug occurred The bug tracking system analyzes about the reported bugs and informs the administrator. 


11. PDB: - Process Database captures the performance data of completed projects.


12. PCB: - Process Capability Baseline summarizes the performance across projects.


13. Capability of a process: - The range of outcomes that can be expected by a project if the process is followed.


14. Jelled Team: - When the design and development groups work together smoothly and efficiently, we call them jelled team.


15. Impact analysis: - Involves identifying work products that need to be changed and evaluating the quantum of change to each; reassessing the project's risks by revisiting the risk management plan and evaluating the overall implications of the changes for effort and schedule estimates; outcome of the analysis is reviewed and approved by customer; change requests are incorporated in the requirements specification document.