Dell project work arrangement

Hello everyone, I am here to provide a brief introduction to the internal software development process of Dell. Dell is not a professional software development company. Its software development process is far from complete, but it also has its advantages in some process control. Let's share it with you today, I also hope to get some suggestions from you. Today, we have some developers from CMMS 3 and CMMS 4. I hope you can give me some suggestions.

Dell's software development project follows another Microsoft MSF (Microsoft Solutions framework) development process.

Project development is divided into five phases: 1. chatting (pre-discussion), 2. envisioning (IMAGINE), 3. planing, 4. developing (Development), 4. stabilizing (stable ). Different roles work collaboratively at each stage.

1. Chatting (pre-discussion) (Project Manager, BA Business Analyst, user)

Pre-project analysis focuses on business analysis. Project managers and users have meetings. First, what do users want to do? Second, are users' ideas feasible? Is it worth doing? If it is worth doing, how much is the budget? The analysis tool is the cost-benefit analysis of CBA (Cost Benefit Analysis). The result is the ROI (return of investment) input-output ratio. In general, the user provides the benefit (Benefit) analysis results and it evaluates the cost (cost) of the project ). The company's current project establishment standard is roi10 to 1. The data I got from the project manager is that about 1/3 of projects can continue.

Milestone: project initiation. (The project is approved by the user department manager and IT department manager. The project is displayed in the project list)

2. envisioning. (IMAGINE) (Project Manager, Business Analyst, user, and Development Team)

Define the project scope. Describe the scope and key functional points of a project, so that the project has a visual outline. At this time, the Project Manager will collect suggestions from various groups. For example, you can contact the development team about the development time, ask the server group for the server type and configuration, and ask the dBA for the database type and configuration.

Milestone: Approved vision scope definition)

3. Planning. (Project Manager, Ba, development group, test group, and Support Group)

Develop detailed project plans. Determine the three elements of the project: time, resources, and scope ". Coupled with risk management.

1. For the project manager, the most important thing is to ask the boss for resources ). Of course, you must determine the exact time for project development.

2. For business analysts, specific business needs need to be clarified. At this time, the system flowchart and user interface sketch will be drawn, and the business description of each function will be added. These are included in SRS (System Requirement Specification.

2. For developers, the most important thing is to develop a development plan and divide the use cases (assign each function point to developers ). Customizes the development schedule and code review plan for each developer.

3. For developers, they also need to define risk management plans and measures. Risks here refer to technical difficulties. Prototype is required for technical difficulties, and some features need to be discarded when risk is too high. (FMEA, Failure Model Effect Analysis) because "errors may occur anywhere ."

4. The test group customizes the test plan based on SRS.

5. The project plan is approved by users, project managers, development managers, and test managers.

Milestone: Approved SRS (System Requirement Specification)

4. Developing. (Project Manager, Development Team, user, server group, Database Administrator)

Design Phase:

1. Development Team: software modeling. Define the system architecture (logical and physical), Domain Modeling, case analysis, sequence diagram analysis for each case, and object modeling. Reevaluate the project complexity. At this stage, the project plan can be adjusted as appropriate.

2. Server group: Install the test server and develop related software. Such as IIS, big IP, and IBM message queue.

3. DBA: install and configure the development database. Configure user accounts: Generally, there are two accounts. The app account is a restricted account running in the official environment. The admin account can be a privileged account for creating database objects.

4. Project Manager: coordinates the work of various teams and checks the progress of each task.

Milestone: approved design document SDS (System Design Specification ).

Encoding phase: Convert the design into code. Adjust and synchronize the design, code review, and review progress based on actual problems.

Milestone: the code passes the unit test and both the Code and documentation are checked in version manager.

Test phase:

1. Sit internal Test, test each scenario based on case description, Analyze memory leakage, optimize system performance, and submit the database performance execution plan to DBA review. Perform stress tests on the system (submit to a stress testing group in Malaysia if necessary ).

Milestone: completion of internal test report and approval from dBA for launch.

2. UAT (User acceptable testing) user test. You can describe each test scenario based on the test case and report system bugs and issues. Developers can fix bugs and determine system impact and business impact based on Issue, appropriately modify the system or record business requirements, and integrate them into future evolution stages based on business priorities.

Milestone: UAT sign off. The user signs for the current system function.

Deployment:

The project manager organizes the documents (design document, SIT test report, UAT sign off, system downtime approval, Server check list, DB checklist. implementation Plan. back out plan (Data & program) to submit a new system launch request to change committee (a committee dedicated to controlling system updates. If change Committee approves the request.

The Development Team deploys a system to the production computer at a specified time, generates a database deployment script, and submits it to the DBA.

The DBA runs the deployment script and provides feedback.

5. stabilizing. (Project Manager, Development Team, and Support Group)

Stable System. The development team records and feedbacks System bugs, and transfers programs and documents to the support group.

Bug fixes: to reduce the impact on production, any bug fixes in the production environment must be approved by change committee. Change Committee only accepts change requests on Tuesday and Thursday afternoons. department managers must approve changes in an emergency. For developers, bug fixing is a very painful task, which also improves the software quality to a certain extent.

Milestone: Support Team sign off.

Roles: User, Project Team Project Manager, BA business analysts, server team server group, DBA database administrator, develop team development group, and support team support group.