1 / 25

Wrapping up the Development Process

Wrapping up the Development Process. Final Delivery – the Go Live / Cut Over Point Process Overview -- SDLC Process Overview – Staging environments Installation / Cutover Strategies Pilot Immediate Phased Parallel Post Mortems – aka Post Implementation Evaluation.

floyd
Télécharger la présentation

Wrapping up the Development Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Wrapping up the Development Process Final Delivery – the Go Live / Cut Over Point Process Overview -- SDLC Process Overview – Staging environments Installation / Cutover Strategies Pilot Immediate Phased Parallel Post Mortems – aka Post Implementation Evaluation

  2. Launch Point for Build Phase • Value of documents • What you learned in collaboration with your stakeholders. • Relationship of trust. • Contractual. Project Charter Analysis & RequirementsSummaries

  3. Process View: SDLC Install / migrate / publish is the last step before the Go Live point

  4. The Build Phase is in the 1st two Staging Environments Go Live

  5. System Testing and User Acceptance Testing Occur in the Production Staging Environment Go Live

  6. USAA has a 4th Staging environment Test system with interfaces with other systems. Test complete system & run User Acceptance tests.

  7. Step 1 – Build a machine in the cloud ?

  8. Install / migrate / deploy Defined as: transfer tested software to production environment aka – Migratetested software to production environment (from a “sandbox” or from a staging environment) aka – Publish aka – Ship – release of new version for vendor aka – Deploy tested software so available to users (only change may be where a url points)

  9. Q1. What term best fits your go live activity for your client project ? Migrate ? Publish ? Ship ? Deploy ?

  10. Q2. What will be the biggest install /go live challenge for your client project ?

  11. Production Environment Reality A large utility company has 3.5 million retail customers Billing is a nightly production run 30 nights a month: 3.5 million/30=116,667 bills nightly Source: UT MIS graduate experience

  12. Production Environment Reality The cycle is tied to daily meter reading for the same 116,667 customers. Billing is a sequential process for geographical areas matched to meter reading assignments.

  13. Production Environment Reality Any production failures are handled as exceptions by a special department, since 117k billscan’t be rerun the same night or the next night. Source: UT MIS graduate about client

  14. Production Environment Reality Imagine having to reboot the system in case of a failure. Source: UT MIS graduate experience

  15. Go Live at user locations for operations Users on site Operations Staff back up db and run efficiency tests & some reports

  16. Go Live for management Managers review on-line data (queries for power users) and periodic reports (daily, monthly, quarterly, annual)

  17. Q3. What operations steps must be considered for your client ?

  18. Cutover Strategies Time Time Time Existing system New system Existing system New system Existing system New system Existing system Pilot system Immediate cutover a. Pilot System strategy Phased cutover Parallel cutover b. Immediate cutover c. Phased cutover d. Parallel cutover Migration Strategy Reading

  19. Installation Strategies

  20. Q4. What is the cutover strategy for your client project ?

  21. Post-Mortems (Post-Implementation Evaluation) Goal: Learn from past successes and failures in order to improve development projects Process Overview: Summarize a project's history Analyze its positive and negative aspects. Source: http://www.gamedev.net/page/resources/_/business/business-and-law-of-game-development/conducting-a-project-postmortem-r977

  22. Post-Mortems (Post-Implementation Evaluation) • Process Steps: • Hold a project review meeting two weeks after the Go Live point. • Document the postmortem in writing. • Begin with a project overview. • Include project details. • Document what went right. • Document what went wrong. • Assess your risk management. • Assess mid-project changes. • Draw meaningful conclusions. • Take action. Source: http://www.gamedev.net/page/resources/_/business/business-and-law-of-game-development/conducting-a-project-postmortem-r977

  23. PostMortems – Every Sprint @ Credera Sprint 1, 2, 3 … n Sprint cycle Sprintplanning meeting Daily cycle • Daily scrum • Daily work Sprint Process Inception Release n • Business case/funding • Vision • Initial product backlog • Initial release plan • Stakeholder buy-in • Assemble team • Logistics Update product backlog Sprint retrospective Product increment Product owner Scrumroles Product backlog Scrum master Scrum artifacts Impediment list Product backlog burndown Sprint review Users Team members Product backlog delta report Sprint backlog Sprint backlog burndown Stakeholders

  24. Pre-Mortems Defined as: Looking at a project to see where it might fail -- before a failure could occur Justin Bell said Credera conducted pre-mortems to examine what the risks might be.

  25. Due Date Reminder Friday, April 13th – deadline to begin an email thread to TAs to arrange a Code & I/O Review to be held Mon. April 23 – Fri. April 27

More Related