1 / 6

Redesign/ Change Management

This project aims to enhance our existing application through a structured redesign process. Over a series of collaborative Joint Application Design (JAD) sessions lasting two weeks, representatives from each department will offer insights and collect requirements. This phase will prioritize the features based on wants versus needs, determining high, medium, and low priorities. Following this, change requests will be raised using Digital Measures, and a dry run will be executed with participants. After validating changes, a go-live date and market feedback analysis will be conducted to ensure a successful implementation.

dudley
Télécharger la présentation

Redesign/ Change Management

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. Redesign/Change Management Team 3

  2. Point of Actions • Joint Application Design (JAD) session (2 weeks) • Representatives from each department • Overview of the existing application • Collect requirements • Additional feedback from departments within 2 weeks • Prioritize/consolidate requirements (1 week) • Wants vs. Needs • High/medium/Low priority • One week

  3. Point of Actions (contd.) • Raise change request Digital Measures (DM) • Consolidate additional requirements from departments. • Raise new requests to DM. • Validate changes by DM. • Dry run with department representatives. • Final request to DM/fixes. • Validate

  4. Point of Actions (contd.) • Go Live to production. • Market Feedback Analysis (MFA) to users. • Analyze MFA results. • Post MFA JAD session (if necessary).

  5. Timeline • Initial JAD session: Jan 23 - Feb 3 • Consolidate requirements: Feb 6 - Feb 10 • Send change request to DM: Feb 10 EOD • Receive additional requirements: Feb 17 EOD • Second change request to DM: March 2 • Validate changes: March 30 • Dry run: April 5

  6. Timeline • Final change requests: April 6 EOD • Validate final changes: April 30 – May 4 • MFA: End of May • Post implementation JAD: TBD

More Related