Work Breakdown Structure
Capstone Project Work Breakdown Structure
Rework Process for Software Development Company
Work Breakdown Structure 1. Rework Process 1.1. Project Management 1.1.1.Validate Project Purpose 1.1.2.Analysis 1.1.2.1. Current Process 1.1.2.2. Current Definitions 1.1.3.Planning 1.1.3.1. Project Proposal 1.1.4.Meetings 1.1.4.1. Project Team 1.1.4.2. Project Sign-off 1.2. Product Requirements 1.2.1.Software 1.2.1.1. JIRA 1.2.1.2. Confluence 1.2.1.3. Outlook 1.3. Development 1.3.1.Software 1.3.1.1. JIRA 1.3.1.1.1. Settings 1.3.1.1.2. Scripts 1.3.2.User Documentation 1.3.2.1. Updated Definitions 1.3.2.1.1. Hotfix 1.3.2.1.2. Patch 1.3.2.1.3. Late Check-in 1.3.2.2. New Process 1.3.2.2.1. Requirements 1.3.2.2.1.1. Request a Hotfix 1.3.2.2.1.2. Request a Patch 1.3.2.2.1.3. Request a Late Check-in 1.3.2.2.2. Steps 1.3.2.2.2.1. Process a Hotfix 1.3.2.2.2.2. Process a Patch 1.3.2.2.2.3. Process a Late Check-in 1.3.3.Training / Presentation 1.3.3.1. Engineering Team 1.3.3.1.1. General training 1.3.3.1.1.1. Updated Definitions 1.3.3.1.1.2. New Process 1.3.3.2. Remaining Teams 1.3.3.2.1. User Documentation
Francisco J. Ayala Bocardo 2016-06-19
Capstone Project Work Breakdown Structure
Rework Process for Software Development Company
1.3.3.2.1.1. Updated Definitions 1.3.3.2.1.2. New Process 1.4. Testing 1.4.1.Software 1.4.1.1. JIRA 1.4.1.1.1. User Interface 1.4.1.1.2. Functionality 1.4.1.1.3. Reporting Capability 1.4.1.2. Outlook 1.4.1.2.1. Notifications 1.5. Launch 1.5.1.Software 1.6. Support 1.6.1.New Process 1.6.1.1.1. Requirements 1.6.1.1.1.1. Request a Hotfix 1.6.1.1.1.2. Request a Patch 1.6.1.1.1.3. Request a Late Check-in 1.6.1.1.2. Steps 1.6.1.1.2.1. Process a Hotfix 1.6.1.1.2.2. Process a Patch 1.6.1.1.2.3. Process a Late Check-in 1.6.2.Software 1.6.2.1. JIRA 1.6.2.1.1. User Interface 1.6.2.1.2. Functionality 1.7. Data 1.7.1.Reporting 1.7.1.1. New Data vs Old Data
Francisco J. Ayala Bocardo 2016-06-19
Rework Process for Software Development Company
Work Breakdown Structure 1. Rework Process 1.1. Project Management 1.1.1.Validate Project Purpose 1.1.2.Analysis 1.1.2.1. Current Process 1.1.2.2. Current Definitions 1.1.3.Planning 1.1.3.1. Project Proposal 1.1.4.Meetings 1.1.4.1. Project Team 1.1.4.2. Project Sign-off 1.2. Product Requirements 1.2.1.Software 1.2.1.1. JIRA 1.2.1.2. Confluence 1.2.1.3. Outlook 1.3. Development 1.3.1.Software 1.3.1.1. JIRA 1.3.1.1.1. Settings 1.3.1.1.2. Scripts 1.3.2.User Documentation 1.3.2.1. Updated Definitions 1.3.2.1.1. Hotfix 1.3.2.1.2. Patch 1.3.2.1.3. Late Check-in 1.3.2.2. New Process 1.3.2.2.1. Requirements 1.3.2.2.1.1. Request a Hotfix 1.3.2.2.1.2. Request a Patch 1.3.2.2.1.3. Request a Late Check-in 1.3.2.2.2. Steps 1.3.2.2.2.1. Process a Hotfix 1.3.2.2.2.2. Process a Patch 1.3.2.2.2.3. Process a Late Check-in 1.3.3.Training / Presentation 1.3.3.1. Engineering Team 1.3.3.1.1. General training 1.3.3.1.1.1. Updated Definitions 1.3.3.1.1.2. New Process 1.3.3.2. Remaining Teams 1.3.3.2.1. User Documentation
Francisco J. Ayala Bocardo 2016-06-19
Capstone Project Work Breakdown Structure
Rework Process for Software Development Company
1.3.3.2.1.1. Updated Definitions 1.3.3.2.1.2. New Process 1.4. Testing 1.4.1.Software 1.4.1.1. JIRA 1.4.1.1.1. User Interface 1.4.1.1.2. Functionality 1.4.1.1.3. Reporting Capability 1.4.1.2. Outlook 1.4.1.2.1. Notifications 1.5. Launch 1.5.1.Software 1.6. Support 1.6.1.New Process 1.6.1.1.1. Requirements 1.6.1.1.1.1. Request a Hotfix 1.6.1.1.1.2. Request a Patch 1.6.1.1.1.3. Request a Late Check-in 1.6.1.1.2. Steps 1.6.1.1.2.1. Process a Hotfix 1.6.1.1.2.2. Process a Patch 1.6.1.1.2.3. Process a Late Check-in 1.6.2.Software 1.6.2.1. JIRA 1.6.2.1.1. User Interface 1.6.2.1.2. Functionality 1.7. Data 1.7.1.Reporting 1.7.1.1. New Data vs Old Data
Francisco J. Ayala Bocardo 2016-06-19
