Procedure to create internal projects clients wo
Download as DOCX, PDF
0 likes41 views
The document outlines an 8 phase procedure for creating internal projects to develop new features based on work done for clients, including gathering requirements, selecting which items to develop, planning, design, development, verification testing, validation, and release of the new features. It also describes a process for creating internal projects to deploy fixes made during support resolutions to the base system. The phases involve activities like requirements gathering, planning, design documentation, development in sprints, testing, and release.
Procedure to create internal projects clients wo
- 1. Procedure tocreate internal projects for development: Projectsbasedonclientsworkorders. Breakdown of Activities by Phase Phase Purpose Activity SD+ Activity Responsibility 1. Items gathering Collect and organize requirements Items will be funneledbasedon work done for clients that deemedto be suitable for the base. Create ticket byan authorized individualinServiceDeskusing the template Release Template Link newrelease ticket to the original client workorder ticket which triggered the change. Choose Internal WorkOrder Type = Integrating clients workorders to base BSR 2. Selection Decided which items will be selected for development Present Internalprojects tickets in the weeklydevelopment group meetingto decide the following: Prioritize items Cancel tickets with irrelevant items. Scheduling items to fall under specific releases. Work assignment and schedule deadlines. Cancel andarchive irrelevant tickets. Provide reasonfor cancellation. Assignscheduledwork to technical team members byDirector of IT or Technical Service Manager Development group 3. Planning Review requirements Determine design phases, activities, andkeydecision points to produce/retrofit the intended feature. Add estimatedtime to the ticket ina note. BSR, Support personnel, TSM 4. Design Define a detailed software requirements Define the detailed feature requirements. Exit criteria: Business Requirements Document (BRD) if required System Requirements Specification(SRS) if required Attach BRD andSRS to the ticket for future reference. BSR, Support personnel
- 2. Breakdown of Activities by Phase Phase Purpose Activity SD+ Activity Responsibility 5. Developme nt Developthe feature Developthe requirement inan iterative manner using sprints. Each sprint includes planning, design, build, andtest activities. For details. Update system verificationtest suites basedon sprint output. Integrate code into the final release. Exit criteria: VerificationTest Suite Validation Test Suite BRD, SRS updated, if required This phase will be addedto SD+ as tasks under the designatedtickets. BSR 6. Verification System level testing Conduct verificationtesting. Check that the completed functionalitymeets the design input requirements. Exit criteria: VerificationReport Completed Verification Test Suites Create verificationtestingrelated tasks under SD+ Support Personnel 7. Validation Evaluate work Deliver and installfunctionally. Exit criteria: Validation Report Completed ValidationTest Suites Create validationtestingrelated tasks under SD+ BSR 8. Release Add feature to Release Conduct final design review and potentiallyaddfunctionalityto release. Add informationrelatedto version control to the ticket Create release task VersionControl Projectsbasedfixesmade duringsupportresolution Technicianwill checkmark the fieldSuitable for the base to indicate that a fix was implementedto a client andit shouldb e deployedto base Link newrelease ticket to the originalclient support ticket which triggeredthe change. Choose Internal WorkOrder Type = Fixes made duringsupport resolution(i.e. whichneeds to go to base)