1 / 7

Solution Vision

Solution Vision. Product Roadmap. Solution Overview. Business Goal 1 (i.e. Reduce time to move case through process) Business Goal 2 (i.e. Eliminate paper forms) Business Goal 3 (i.e. Improve customer satisfaction) Business Goal 4 (i.e. Standardize process across organization).

amia
Télécharger la présentation

Solution Vision

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. Solution Vision Product Roadmap

  2. Solution Overview Business Goal 1 (i.e. Reduce time to move case through process) Business Goal 2 (i.e. Eliminate paper forms) Business Goal 3 (i.e. Improve customer satisfaction) Business Goal 4 (i.e. Standardize process across organization) Solution Vision: This is a high-level description of the vision for the solution as a whole. Each solution has one or a few key goals, or “what’s in it for me” offerings for the customer. This is why the project exists in the first place, and what should be presented here.

  3. Presentation Key Key Features/Enhancements for Release x: To meet the client’s business needs, a solution has been defined with numerous features that vary in importance as it relates to meeting the key business objectives. The goal of a Solution Vision is to organize features by priority, and ensure that the most critical features are included as in scope for the project. The following key defines how features are presented in relation to their priority. • Text Items in Black/Bold: • Indicate Target Areas for the next release, considered high-priority or “core” to the release. These features define a release. Priority 1 • Text in Dark Grey/Italic: • Indicate items for a known Phase 2, or items where development is on-going/in-progress with a likely partial completion. These items are planned to some degree, but are lower in priority than black items. These would not be considered “core” requirements. This is all negotiable based on client feedback and a client’s changing needs. Priority 2 • Text Items in Grey/Italic: • Indicate Target Areas for a future release, categorized as lower priority in the short term, nice-to-have, or not well enough defined for inclusion in the current release. Future

  4. Solution Objectives Key Epics/Functional Objectives for Final Solution (or for Release x): The following Epics or Feature Categories highlight the 10,000 foot view of a solution. It is the solution’s elevator pitch. This type of information may be found in a Project Work Statement (PWS), may have been derived from SME sessions, but likely is a combination. This will be a relatively short list, and will likely coincide loosely with the vertical lane titles on the SDD. • Epic 1 (i.e. Establishing Cases) • Epic 2 (i.e. Developing Cases) • Epic 3 (i.e. Adjudicating Cases) • Epic 4 (i.e. Rating Cases) • Epic 5 (i.e. Generating Awards) • Epic 6 (i.e. Archiving Cases)

  5. Feature Implementation: (Next Steps) Prioritized Items for Solution (or could be fore Release X) The Vision Deck needs to paint a clear picture of prioritized features or even “Next Steps”, which would be for an interim deck or for a deck where the customer is wanting a view of a sprint or a release. This type of slide may have a little more detail, and contain key User Story titles (not user story format). This is a key slide for painting a high level picture of what is being targeted “for sure” and what is next in line “if we have time”. This may take a couple slides, or even a slide per type (priority 1, priority 2, for future consideration/definition). • Feature 1 (i.e. Create all user roles and permissions) • Feature 2 (i.e. Enable creation of case files) • Feature 3 (i.e. Establish core inboxes) • Feature 4 (i.e. Create initial ad hoc routing window) • Feature 5 (i.e. Enable uploading of documents into case file) • Feature 6 (i.e. Enable printing of case file contents) Priority 1 • Feature 7 (i.e. Enable automatically generated email notifications) • Feature 8 (i.e. Enable 2-way interface with legacy database) • Feature 9 (i.e. Enable configuration capabilities to direct workflow) • Feature 10 (i.e. Enable online signature capabilities) Priority 2

  6. Feature 1 (Ex. “Creating a Case File”) <Feature Description> Each Feature Description Page puts bullets for each feature, breaking it down a little more into recognizable tasks. Here you can see for a feature (i.e. Creating a Case File) what key things it entails as being proposed. If a UI exists, or Mock exists, it can be included to enhance effectiveness, or to show a before/after scenario. (Features will be loosely related to items represented within each vertical column on the SDD, in the description and the pictorial representation, and Tasks listed here are akin to User Story titles. Only significant items would be listed here.) • User Story Title 1 (i.e. Manual establishment of a new case) • User Story Title 2 (i.e. Manual entry of key data that defines a case) Priority 1 FEATURE DESCRIPTION • User Story Title 3 (i.e. Ability to color-code case file icons based on case type) Priority 2 • User Story Title 4 (i.e. Pre-population of New Case information from x system interface) Future

  7. Ex. As Is “Creating a Claim” <AS IS description>. This type of slide works great for subsequent decks, which need to show at a VERY HIGH LEVEL where a solution is as well as where it is going. This slide would be followed by a “Next Steps for this Feature. FEATURE DESCRIPTION • Enter Establishment details • Required Fields/Data Validation directs users • Click Establish Claim button to establish claim

More Related