1 / 26

IIBA – November Breakfast

IIBA – November Breakfast. “Out of the Box: Positioning Business Analysts for Success with Package Software” November 2 nd , 2012. Agenda. Introductions Why are we here? What is Package Software? What are the Benefits of a Package? Building an Example

aelwen
Download Presentation

IIBA – November Breakfast

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. IIBA – November Breakfast “Out of the Box: Positioning Business Analysts for Success with Package Software” November 2nd, 2012

  2. Agenda • Introductions • Why are we here? • What is Package Software? • What are the Benefits of a Package? • Building an Example • What are the challenges in implementing Packages? • How do packages change the BA role? • Analysis Phase Changes • Relationship and Role Adjustments • Tips and Tricks

  3. Introductions Kenneth Schumann Manager, Package Center of Excellence Mikayla Rettig Sr. Business Analyst, Merchandising for Canada Lori Salberg Business Consultant, Finance

  4. Why are we here? • Companies are making a shift and selecting more packaged software solutions to solve their business problems • The largest software companies in the world together generated software revenues of over $235 billion in 2010, an increase of 7% compared to 2009 ($220 billion)- Software Top 100 Edition 2011 • Package software has been available for 50 years • Originated in highly rules driven systems such as Payroll and Finance • Expanded in the 1990s to deliver in all aspects of a business • Packages are filling more niche or specific business problems

  5. What is Package Software Package software is software that is ready-made and available for sale, lease or license to the general public. Also referred to as Commercially off The Shelf (COTS) software • Not unique to business processes – Commodity • Brings industry best practice – Community Support • Include features that can be expanded into in the future • Continuous R & D • Customize only for critical requirements

  6. What are the Benefits of Package • Best Practices Embedded in Software • Common Solution Across Business Operations • Regulatory Requirements Maintained by Vendor • Outsource accountability for support, lifecycle and operability • Speed to Market

  7. Building an Example You want to build a house. You can chose between building from the foundation up or you can have a factory built home. One of your requirements might be it must have a bathroom. Example of Requirements • Build a bathroom

  8. Building an Example You want to build a house. You can chose between building from the foundation up or you can have a factory built home. One of your requirements might be it must have a bathroom. Example of Requirements • Build a bathroom • Must have a linen closet

  9. Building an Example You want to build a house. You can chose between building from the foundation up or you can have a factory built home. One of your requirements might be it must have a bathroom. Example of Requirements • Build a bathroom • Must have a linen closet • Must be blue

  10. Building an Example You want to build a house. You can chose between building from the foundation up or you can have a factory built home. One of your requirements might be it must have a bathroom. Example of Requirements • Build a bathroom • Must have a linen closet • Must be blue • Must have a toilet

  11. Building an Example You want to build a house. You can chose between building from the foundation up or you can have a factory built home. One of your requirements might be it must have a bathroom. Example of Requirements • Build a bathroom • Must have a linen closet • Must be blue • Must have a toilet • Must have a sink

  12. Building an Example You want to build a house. You can chose between building from the foundation up or you can have a factory built home. One of your requirements might be it must have a bathroom. Example of Requirements • Build a bathroom • Must have a linen closet • Must be blue • Must have a toilet • Must have a sink • Must have a shower

  13. Building an Example You want to build a house. You can chose between building from the foundation up or you can have a factory built home. One of your requirements might be it must have a bathroom. Example of Requirements • Build a bathroom • Must have a linen closet • Must be blue • Must have a toilet • Must face north • Must have a sink • Must have a shower

  14. Building an Example You want to build a house. You can chose between building from the foundation up or you can have a factory built home. One of your requirements might be it must have a bathroom. Example of Requirements • Build a bathroom • Must have a linen closet • Must be blue • Must have a toilet • Must face north • Must have a sink • Must have a double sink • Must have a shower

  15. Building an Example You want to build a house. You can chose between building from the foundation up or you can have a factory built home. One of your requirements might be it must have a bathroom. Example of Requirements • Build a bathroom • Must have a linen closet • Must be blue • Must have a toilet • Must face north • Must have a sink • Must have a double sink • Must have a shower • Must have a tub

  16. Building an Example You want to build a house. You can chose between building from the foundation up or you can have a factory built home. One of your requirements might be it must have a bathroom. Example of Requirements • Build a bathroom • Must have a linen closet • Move into hall • Must be blue • Must have a toilet • Must face north • Must have a sink • Must have a double sink • Must have a shower • Must have a tub • Must have separate shower

  17. Building an Example You want to build a house. You can chose between building from the foundation up or you can have a factory built home. One of your requirements might be it must have a bathroom. Example of Requirements • Build a bathroom • Must have a linen closet – Fit • Must be blue – Fit - Configuration • Must have a toilet - Fit • Nice to face north – Fit • Must have a sink - Fit • Nice to have a double sink – Fit/Gap – Configuration/Customization • Must have a shower - Fit • Nice to have a tub – Gap - Customization • Nice have separate shower – Gap - Customization

  18. Package Implementation Challanges • Recognize you have a cultural change initiative • Look at people and process not just technology • Obtain strong sponsorship from leaders • Minimal in house experience with package solution • Avoid over customization • Understanding critical requirements • Underestimating implementation • Overlooking scalability and performance

  19. How does the BA role change? Biggest changes to the BA role come in the Analysis Phase • Conversation changes from “What do you want?” to “Here’s what it does. What are the gaps?” • Mapping exercise vs. building exercise • More problem solving than custom development • Process re-engineering is part of analysis discussion • Introduction of gap identification and analysis

  20. Analysis Phase for Package Determine Configuration and Gaps in the system Package Terminology • As Is Process Flow – Process of current system • To Be Process Flow – Process of new package • Conference Room Pilot (CRP) • Fit/Gap Assessment • Configuration • Customization • PRICEFW • Options for Gap Resolution • Remove Requirement • Defer Requirement • Re-engineer Business Process • Customize Package

  21. How can a BA adjust? • Involve business teams early • Understand reason behind requirements to determine criticality and priority levels • Bring multiple solutions to the table • Think about how it can be done differently – business needs to be able to understand and visualize the end state • Develop a strict gap process • Defined approval process • Need to prove “why customization”? • It is a cost/benefit analysis • Use proof of concepts to demonstrate functionality

  22. Configuration vs. Customization Many packages permit and require a certain amount of switches & levers to be maintained or configured, allowing a level of individualization for business processes & different industry requirements. It is paramount to come to a consensus of what defines “configuration” vs “customization” at the onset of a package implementation. • Typical customization item: • Change that requires additional code • The change needs to be analyzed before applying an upgrade or patch • The change requires IT involvement for future upgrades • Typical configuration item: • Change is limited to enabling functionality through system setting • Maintenance of the configuration can be transitioned and owned by the business

  23. Rationalizing Customization • Value Prop - What is the value of making this change? • Cost Dimension-What is the impact of making this change in these areas? • Customization Impact Level - What is the impact to the overall health of the product?

  24. Tips and Tricks • Discuss role expectations, communication & escalation plans up front with sponsor • Consider people and process not just technology • Don’t underestimate the cultural change initiative • BA needs to have a strong understanding of the business process • Avoid over customization by identifying critical requirements early • Understanding how the business will react & prepare them to compromise, embracing a “best for the organization” mentality • Use experienced resources who understand range of package vs. process options and can mentor internal resources

  25. Q & A ?

  26. Wrap-up Thank you!

More Related