Excerpted from: 32-hour customs clearance for information system projects (only for learning and communication, infringement deleted!)
The impact of organizational structure on the project
Basic knowledge points
- Project-based organizations mean that their business is mainly composed of projects, which can be divided into two categories:
(1) Its main income comes from organizations that perform projects for others in accordance with the contract.
(2) Organizations that adopt the project system for management. - Organizational structure.
The key characteristics of the main types of enterprise organization structure related to the project are shown in the following table.
| Project characteristics/organization type | Functional organization | Matrix type | Project organization | ||
|---|---|---|---|---|---|
| Weak matrix organization | Balanced organization | Strong matrix organization | |||
| Project manager's rights | Little or no | limited | Small to medium | Medium to large | Big to full power |
| Proportion of employees in the organization who participate in project work full-time | No | 0%~25% | 15%~60% | 50%~95% | 85%~100% |
| Project manager position | Part time | Part time | Full time | Full time | Full time |
| General title of the project manager | Project Coordinator/Project Supervisor | Project Coordinator/Project Supervisor | Project Manager/Project Director | Project Manager/Plan Manager | Project Manager/Plan Manager |
| Project management/administrative staff | Part time | Part time | Part time | Full time | Full time |
- Functional organization
- Project organization
- Weak matrix organization
- Balanced matrix organization
- Strong matrix organization
- Compound organization
The life cycle of an information system project
Basic knowledge points
- The characteristics of the project life cycle structure of general projects.
(1) Cost and manpower input are relatively low at the beginning, reach the highest during the execution of the work, and quickly fall back when the project is about to end.
(2) Risk and uncertainty are greatest at the beginning of the project, and gradually decrease with the designation of decisions and the acceptance of deliverables during the entire life cycle of the project.
- The relationship between stage and stage.
There are two types of relationship between stages: sequence relationship and overlap relationship.
In the overlap relationship, a stage starts before the completion of the previous stage, which can be used as a technique for schedule compression and is called "quick follow-up".
Overlapping phases may require additional resources to carry out work in parallel, which may increase risks, and may also cause rework due to starting follow-up work without obtaining accurate information from the previous phase.
Typical life cycle model of information system project
Basic knowledge points
- The waterfall model is a classic software life cycle model. Software development is generally divided into: feasibility analysis (plan), requirements analysis, software design (outline design, detailed design), coding (including unit testing), testing, operation and maintenance, etc. Six stages.
- The spiral model is an evolutionary software model that combines the iterative characteristics of the prototype implementation with the controlled and systematic aspects of the linear sequence (waterfall) model, which makes the rapid development of software incremental versions possible.
The four quadrants of the spiral model represent the four phases of each cycle: planning, risk analysis, implementation engineering, and customer evaluation. The spiral model emphasizes risk analysis, and is especially suitable for large, complex, and high-risk systems.
- The four phases of the life cycle of the iterative model: initial, refinement, construction, and handover, which can be further described as cycle (CyCle), phase (Phase), and iteration (Interation). The core workflow describes the static components of the iterative model from a technical perspective, including: business modeling, requirements acquisition, analysis and design, implementation, testing, and deployment.
- The V model is a symmetrical structure, which clearly shows the different levels in the testing process, and very clearly describes the correspondence between these testing phases and development phases.
(1) Unit testing. Generally executed by the developer, the smallest test unit is set first, and then the correctness of each unit function is verified by designing corresponding test cases.
(2) Integration test. The main concern is that the system can be successfully compiled, the main business functions are realized, and the data between the various modules of the system can communicate normally.
(3) System testing to verify whether the entire system meets the requirements specifications.
(4) Acceptance test to monitor whether the system meets the requirements defined in the contract or user needs from the user's perspective.
-
Features of the V model.
(1) The main idea is that development and testing are equally important, with the left side representing development activities and the right side representing testing activities.
(2) There is a test level corresponding to each development stage.
(3) Testing is still a stage in the development life cycle. Unlike the waterfall model, there are multiple testing levels corresponding to development levels.
(4) Applicable to situations where the requirements are clear and the requirements are not frequently changed. -
The prototype method believes that when it is difficult to put forward user needs in a comprehensive and accurate manner immediately, it does not require a comprehensive and detailed investigation and analysis of the system, but instead develops a prototype system quickly based on the developer's preliminary understanding of user needs Through repeated modifications to achieve the user's final system requirements.
The features of the prototype are as follows:
(1) Practical.
(2) Have the basic characteristics of the final system
(3) Convenient, fast and low cost construction
- Agile development takes the evolution of user needs as the core and adopts an iterative and gradual approach to software development. In other words, a large project is divided into multiple small projects that are interrelated but can also run independently, and complete them separately. During this process, the software is always in a usable state.
- Principles of agile development.
(1) Rapid iteration
(2) Let testers and developers participate in requirements discussion
(3) Write testable requirements documents
(4) Communicate more and minimize documents
(5) Make product prototypes
(6) Consider testing early
Single project management process
Basic knowledge points
- The five process groups composed of the processes of project management can correspond to the PDCA cycle, that is, the Deming circle: "Plan-Do-Check-Act" cycle.
- The project management process group includes five: the start process group, the planning process group, the execution process group, the supervision and control process group, and the closing process group.
(1) The initiation process group defines and approves the project or project phase, including the two processes of "making the project charter" and "identifying the project stakeholders".
(2) The planning process group defines and refines the goals, and plans the necessary course of action to achieve the goals to be achieved and the scope of the problems to be solved to complete the project.
(3) The execution process group integrates personnel and other resources, and executes the project management plan during the life of the project or at a certain stage.
(4) The supervision and control process group requires regular measurement and monitoring of project performance, identification of deviations from the project management plan, so that corrective measures can be taken when necessary to ensure that the project or phase objectives are achieved.
(5) The closing process group formally accepts products, services or work results, and ends the project or project phase in an orderly manner. - Comparison table of ten knowledge areas of five process groups of project management
| Knowledge field | start up | plan | carried out | control | ending |
|---|---|---|---|---|---|
| Overall project management | Develop project charter | Preparation of project management plan | Direct and manage project execution | Monitoring project work, overall change control | Project closing |
| Project scope management | Prepare scope management plan, collect requirements, scope definition, establish WBS | Scope verification, scope control | |||
| Project time management | Preparation of schedule management plan, activity definition, activity sequencing, resource estimation, diachronic estimation, designated schedule plan | Cost Control | |||
| Project cost management | Prepare cost management plans, cost estimates, and cost budgets | Cost Control | |||
| Project quality management | Develop a quality management plan | Quality assurance | QC | ||
| human resource Management | Develop a human resource plan | Personnel acquisition, team development | Manage the project team | ||
| Project communication management | Communication plan | Management communication | Control communication | ||
| Project risk management | Specify risk management plan, risk identification, risk qualitative analysis, risk quantitative analysis, risk response plan | Risk monitoring | |||
| Project procurement management | Preparation of procurement management plan | Implement procurement | Control purchases | End purchase | |
| Stakeholder Management | Identify stakeholders | Prepare a stakeholder management plan | Management stakeholder participation | Control stakeholder participation |