Presentation is loading. Please wait.

Presentation is loading. Please wait.

Value across the entire software project lifecycle

Similar presentations

Presentation on theme: "Value across the entire software project lifecycle"— Presentation transcript:

1 Value across the entire software project lifecycle
Planning Analysis & Requirements Design & Configuration Implementation & Testing Final Preparation & Go Live Post-Deployment & Support Performance Assessment & Adjustment Value across the entire software project lifecycle Epilogue is a complete solution for capturing and documenting how key enterprise systems work. Capturing and transferring knowledge is critical at every stage in the software project lifecycle. This brief slide show will show you how. 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.

2 Enterprise Application Success
Effective user adoption is key to achieving software ROI … yet most organizations don’t have the time or resources to effectively educate employees on a new technology. (Gartner, 2010) Defining Enterprise Software Success, Neochange , Technology Services Industry Association, 2008 50% of polled entities who’ve deployed ERP solutions have realized 50% or less of the projected benefits from their system. (Panorama Consulting, 2012) In 2008, this key study found the number one factor for realizing software value is effective user adoption. CLICK: Unfortunately, Gartner concludes that most organizations don’t have the time or resources to effectively educate employees on a new technology. CLICK: And Panorama Consulting, who does an annual report on the state of ERP, said 50% of organizations in their 2012 study realized 50% or less of their projected benefits from their system. 2

3 Who affects Effective End User Adoption
Training End User Helpdesk Development Project Management Functional Team Organization Change Management Systems Integration Whether you are in systems integration, development, project management, a functional team, organization change management, training, support, or an end user you play a role in contributing to or detracting from effective user adoption. 3

4 Maslow’s Hierarchy of Needs (for effective user adoption)
Software’s Maslow’s Hierarchy of Needs (for effective user adoption) Physiological Needs (breathing, eating, sleeping) Safety Needs (shelter, work, family, health) Social Needs (friends, family, intimacy) Esteem Needs (self-esteem, confidence, respect achievement, etc.) Self Actualization (morality, creativity, problem solving, spontaneity, lack of prejudice) Maslow’s Hierarchy Transaction Level (understanding what basic systems building blocks, the transactions, will provide the most fundamental execution) Operational Entity Level (understanding what tactical execution is needed to achieve the systems strategies) Strategy Level (understanding what systems strategies are likely to lead to organizational success) Process Level (understanding what systems processes are required to execute the tactics by functional level) Functional Level (understanding how to execute functional tactics to contribute to success at the operational entity level) Effective User Adoption Hierarchy We all learned about Maslow’s Hierarchy of needs where certain needs must be taken care of first to allow us to elevate to higher levels. CLICK: We suggest that achieving effective user adoption also has some fundamental needs that need to be taken care of first and that begins with a solid foundation. CLICK: We believe that foundation is where your end-users work - at the transaction and process level. 4

5 Complete Platform for Software Documentation
As a complete platform for software documentation, Epilogue is comprised of three components, Author, Publisher and Advisor. CLICK: Epilogue Author captures and records how your application works, not like screen recorder and screen capture tools like Captivate, Camtasia or Snagit, but digging deeper into your application and providing real information about how your application works from a users point of view. CLICK: Epilogue Publisher is the web-based engine serving several purposes, content repository, review/QA workflow manager, and systems administration for monitoring, reporting and overall process management. CLICK: Lastly, Epilogue Advisor automatically delivers content to end-users in real-time as they are working in your key enterprise applications, making it effortless for them to get the help and guidance they need, when they need it. 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 Planning Analysis & Requirements Design & Configuration Implementation & Testing Final Preparation & Go Live Post-Deployment & Support Performance Assessment & Adjustment 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. Here’s a generic software project lifecycle showing our utility in every phase. CLICK: Planning teams can actually document the Current state, reducing the risk of starting with a false starting point which can have negative ripple effect on the Future State. CLICK: Project and Build Teams eliminate unnecessary iterations and extended cycle times cause by miscommunication between the build team and functional reviewers by using Epilogue to document functional builds for review and feedback. CLICK: In User Acceptance Testing, we visually capture testing failures and route these back to the implementation team providing complete clarity. Once testing is passed, you’ve also got a huge jump on the required baseline documentation. CLICK: The Training Team achieves dramatic productivity gains and volume increases giving End Users much deeper coverage of their applications. CLICK: By having real-time and deep content at their fingertips, End User learning retention is at it’s peak and support volume is driven down. Support also has a tool to continue to document the application in areas that have the highest support activity. CLICK: Lastly, Operational Management and Training get important data for training focus and end user proficiency in specific transactions. 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
Authors = Project Team Implementation Team Training Team Support Team START HERE AND GO  Epilogue Author Create, review, edit & enhance Record your application’s functionality, transactions, processes Reviewers = Functional Reps, UAT team, Training content approvers Epilogue Publisher’s Approval Dashboard Initiate Review Process Prompts review Epilogue Publisher Epilogue Publisher Reviewer feedback provided in the HTML version Rejected Epilogue Publisher’s Feedback Dashboard 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 Content is pushed to end-users as they work in their applications Approved Here’s how we do it. CLICK: It starts with Epilogue Author. CLICK: Epilogue Author sits in the background and captures everything the Author does as they work through the application. After recording, the Author can easily review, edit and enhance their content as needed to meet the need of that recording purpose. CLICK: Upon saving to Epilogue Publisher, a review and approval process kicks off, facilitated by Epilogue Publisher’s workflow and monitoring capabilities. CLICK: Reviewers either accept or reject the work. When rejected, the reviewers have the opportunity to easily insert comments to provide specific feedback, which is captured in a dashboard and routed back the Authors for review and adjustment. CLICK: Once approved, the documentation is put into production which means different things depending on the project phase. It can mean the current state is documented, the designed functionality meets the spec, user acceptance testing has passed, or end user documentation is available to end users and support. Rejected 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 Epilogue Publisher also provides the means for systems administration and what I call “air traffic control”. CLICK: We monitor all aspects of content creation. CLICK: We monitor utilization and enable you to slice and dice that information for key insight. CLICK: We track end user proficiency in key transactions via our simulation testing capability. CLICK: We also enable End User feedback to the system administrator and documentation team for error correction and continuous improvement suggestions. The purpose is to arm you with a platform to manage your content and provide business insight into how to improve effective user adoption. 8

9 Built for the SIZE of the Problem
The studies show that effective user adoption is the key. For complex systems, the size of the problem is the barrier. We’re built for the size of the problem. For more information, please contact us at or check out some of our other brief slideshows. Thank you. THANK YOU for more information 9

Download ppt "Value across the entire software project lifecycle"

Similar presentations

Ads by Google