1 / 9

Planning Analysis & Requirements

Capture and transfer knowledge at every stage in the software project lifecycle. Offset the negative impact on iterations, cycle times, risk and cost. Enable effective user adoption and achieve operational effectiveness of key enterprise systems. Planning Analysis & Requirements.

hagop
Télécharger la présentation

Planning Analysis & Requirements

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. Capture and transfer knowledge at every stage in the software project lifecycle.Offset the negative impact on iterations, cycle times, risk and cost.Enable effective user adoption and achieve operational effectiveness of key enterprise systems. • Planning Analysis & Requirements Value across the entire software project lifecycle • Design & Configuration • Performance Assessment & Adjustment • Post-Deployment & Support • Implementation & Testing • Final Preparation & Go Live

  2. Enterprise Application Success Effective user adoption is key to achieving software ROI … yet most organizations don’t have the time or resourcesto effectively educate employees on a new technology. (Gartner, 2010) 50% of polled entities who’ve deployed ERP solutions have realized 50% or less of the projected benefits from their system. (Panorama Consulting, 2012) Defining Enterprise Software Success SandHill.com, Neochange , Technology Services Industry Association, 2008 2

  3. Who affects Effective End User Adoption Systems Integration Organization Change Management Project Management Helpdesk End User Development Functional Team Training 3

  4. Software’s Maslow’s Hierarchy of Needs(for effective user adoption) Maslow’s Hierarchy Effective User Adoption Hierarchy Self Actualization (morality, creativity, problem solving, spontaneity, lack of prejudice) Strategy Level (understanding what systems strategies are likely to lead to organizational success) Operational Entity Level (understanding what tactical execution is needed to achieve the systems strategies) Esteem Needs (self-esteem, confidence, respect achievement, etc.) Functional Level (understanding how to execute functional tactics to contribute to success at the operational entity level) Social Needs (friends, family, intimacy) Process Level (understanding what systems processes are required to execute the tactics by functional level) Safety Needs (shelter, work, family, health) Transaction Level (understanding what basic systems building blocks, the transactions, will provide the most fundamental execution) Physiological Needs (breathing, eating, sleeping) 4

  5. Complete Platform for Software Documentation 5

  6. Epilogue value across the software project lifecycle The Planning Team – Equip SMEs with tools to easily capture the Current State to facilitate Future State design and prototyping, reduces risk caused by being out of synch with the actual Current State Operational Mgmt and Training – input for end user training focus and specific end use proficiency issues. The Project and Build Teams – reduces risk caused by inaccurate review and feedback associated with functionality reviews, reducing iterations and cycle times. The Implementation Effort – reduces risk and delays associated with inefficient and imprecise communication of testing failures. For testing passes, also provides a jump on baseline training documentation. End Users and Support– deep help content delivered to end users in real time in the target application, reducing Support volume Support has this at their fingertips as well. The Training Team and End Users – more of the target application is documented and available for training, help and support, reducing documentation time 50-90% 6

  7. General Epilogue Workflow • START HERE AND GO  Epilogue Author • Epilogue Publisher • Epilogue Publisher • Authors = • Project Team • Implementation Team • Training Team • Support Team Record your application’s functionality, transactions, processes • Approved means: • The current state is accurately captured • The configuration/design work meets the spec • UAT is completed and documented • Training, help and support documentation is ready for release Create, review, edit & enhance • Initiate Review Process • Content is pushed to end-users as they work in their applications Epilogue Publisher’s Feedback Dashboard Epilogue Publisher’s Approval Dashboard • Prompts review • Rejected • Rejected Reviewer feedback provided in the HTML version • Reviewers = Functional Reps, UAT team, Training content approvers • Approved 7

  8. Epilogue’s “Air Traffic Control” Track the status of all content creation and where it stands in the QA workflow and publishing process • Track what content is being used and who’s using it • Use the Testing mode of simulation and track user proficiency scores over time. SCORM compliant export of scores and simulations to any LMS • User feedback for error correction and process improvement suggestions 8

  9. Built for the SIZE of the Problem THANK YOU info@epiloguesystems.com for more information 9

More Related