Build vs. Buy WSATA Panel Discussion

Slides:



Advertisements
Similar presentations
Tales from the Lab: Experiences and Methodology Demand Technology User Group December 5, 2005 Ellen Friedman SRM Associates, Ltd.
Advertisements

Achieve Benefit from IT Projects. Aim This presentation is prepared to support and give a general overview of the ‘How to Achieve Benefits from IT Projects’
Quality Education for a Healthier Scotland Getting Knowledge into Action for Person-Centred Care Bibliotherapy in NHSScotland 23 rd September 2013.
AgileMan Consulting So what the heck is Agile? It came about as a response to the high failure rate of software projects (> 60%), where failure means late,
Envision – Architect – Prove Scott Mauvais Technical Director Microsoft Technology Center.
David Boyd & Associates Integrated Tax System Procurement Assistance David Boyd & Associates.
GAI Proprietary Information
Service Provisioning Service Provider Consulting Microsoft Consulting Services harvests the knowledge, experience, and tools established by designing and.
Systems Development (SD) Presentation Michael Webb IT Director for Medicaid Utah Department of Health UDOH Informatics Brownbag August.
Introduction to Systems Analysis and Design
Embedding Security into a Software Development Methodology April 5 th, 8:30 AM Jonathan Minter Director, IT Development and Engineering Liberty University.
© Copyright High Performance Concepts, Inc. 12 Criteria for Software Vendor Selection July 14, 2014 prepared by: Brian Savoie Vice President HIGH.
Effective Methods for Software and Systems Integration
Software Development Process
BTS730 Communications Management Chapter 10, Information Technology Management, 5ed.
1 Make vs. Buy The purpose of this section is not to make a firm recommendation as to whether to recommend COTS or bespoke packages, but rather to discuss.
Alternatives to Systems Development Chapter 11. Chapter Objectives Understand the factors and situations where building a system in-house is not feasible.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Industry SDLCs and Business Climate. Justin Kalicharan Credentials Director and Senior Technology Officer Over 14 years of coding experience in various.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Practice Management Quality Control
Strategically Managing the HRM Function McGraw-Hill/Irwin ©2012 The McGraw-Hill Companies, All Rights Reserved.
1 Managed IT Services Sharing my knowledge and experiences Tom Smyth – Chairman and Managing Director.
Agile: Lessons Learned (a retrospective) Tony
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
Workforce Scheduling Release 5.0 for Windows Implementation Overview OWS Development Team.
1 Computing and Communications Services ● Business Analysis and Process Re-engineering Gayleen Gray, Deputy CIO.
10 key principles of agile software development
CS223: Software Engineering Lecture 16: The Agile Methodology.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Successful Software Practice How to successfully work as a team to create software Chris Mendes, Chief Technology Officer Sirca Limited March 2012.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Lecture Outline 12 Other ways of obtaining systems IS Department in a Business Organization The Future of IS.
ITEC 275 Computer Networks – Switching, Routing, and WANs
Key features of an effective Compliance Strategy
Principles of Information Systems Eighth Edition
Agile Culture Instructor Pilot ISA 301 March 2017 Robert Thomas.
Aligning Business Strategy and IT Strategy Gerhard Barth
Defining the Playing Field: “What is Strategy”
Week 11 Organizing Information Technology Resources
Feed Forward An Approach to Marking from PIXL contributor
Empowernomics™ Business Transformation with Outstanding Economic Impact Building Intelligent, Inspired, Empower Organizastions e-Ecosystems, INC
Intelligent Systems Development
It’s not all about the tool!
Company EMC Headquarters Hopkinton, Massachusetts Industry High tech
A CIO’s view of SDN Who are REANNZ Current Maturity of SDN (top-down)
SOA Implementation and Testing Summary
The Transportation Information Gateway An Open Source Web Platform for Collaboration in the Planning Process AMPO 2017 Annual Meeting Brian ten Siethoff,
The Organizational Context: Strategy, Structure, and Culture
The Key to Hiring Excellence “The act of working together to achieve a common purpose.” —Oxford Dictionary.
How to Successfully Implement an Agile Project
Critical Changes to PMBOK6
Today’s Business Pain Points
CIS12-3 IT Project Management
IS&T Project Reviews September 9, 2004.
Monday 9th April – Friday 13th April 2018
Gathering Systems Requirements
Introduction to Agile Blue Ocean Workshops.
OO Design and Development
Project management Learning Unit 5.
What is Interesting in the CCSP certification?
Getting Knowledge into Action for Person-Centred Care
A Focus on Strategic vs. Tactical Action for Boards
Gathering Systems Requirements
IST346: What Is IT?.
The Organizational Context: Strategy, Structure, and Culture
The Organizational Context: Strategy, Structure, and Culture
The Organizational Context: Strategy, Structure, and Culture
Part I: Service Oriented Architecture
INTERNATIONAL GENDER UNIT
Presentation transcript:

Build vs. Buy WSATA Panel Discussion Brian Ridderbush, Senior Manager

Questions Assigned (Agenda)  Vendor Understanding of Agency Requirements  System Capacity and Expandability Some Research for Presentation Large Research and Consulting Organization (2) CIO’s from Largest Tax Agencies in the U.S. 30+ Years as Vendor, Project Manager, Director

Question #1 Vendor Understanding of Agency Requirements Starts with a good RFP; be detailed and ask for everything you need Work with a Partner that understands your business Demand Project Managers and Subject Matter Experts, BA’s, etc. that have Tax Experience Concept of a “Tax Binder” Every form, report, agency policy and statute Working set of business rules brought to engagement reflective of the requirements in RFP, Contract and Tax Binder Iterative Approach to Validating Requirements, Functionality and Testing

Questions Vendor Understanding of Agency Requirements Implementation Methodology

Question #2 System Capacity and Expandability Scalability is provide by fact vendor is developing for all size agencies “Scale up” is available today by hardware, N-Tier architecture Design, Code and Tools still need to be engineered to scale Performance Test and Benchmark

Question #2 System Capacity and Expandability Rule Management Systems Centralizes an agency’s business rules Flattens rule development process Enables collaboration between users, analysts and technical personnel Empowers changes not previously envisioned Does not carry forward undesired business logic Allows choices in rule construction – table, decision tree, … Speeds deployment Simplifies testing Provides for simulation

Large Research and Consulting Firm Perspectives Encourages Planning and Visioning as a Guiding Principle Submits that “Plan and Vision will Dictate the Approach” “Its about a trajectory and target goal. I want to be healthy and in shape. What does that mean? Exercise 4 times a week? Eat better? How am I going to check on my progress? It’s the same for any business. Vision Expected Outcomes Am I really ready to do it? Its’ pervasive How ready am I to do this? Can I manage it? Am I ready? Organization Readiness, for example, Do I Have a PMO? Where am I going and how do I know when I’m there? Custom Software = equals a lot more details, a lot of control, and staff may or may not be able Business of government is not often skilled to do software development

Large State Tax Department CIO’s Perspectives Best thing about COTS is it brings to an agency Best Practices; built around knowledge from vendors built and installed in multiple jurisdictions Problem with Custom is “paving the cow path” over and over; build up bad practices over time Vendor who has built the system (hopefully) is engaged on your project and advising you on the way to do things Custom – all you get is a suite of software, a lot of ‘crap’ and having to play system integrator and make it work! Quicker start up time with COTS, flexibility to change it, and iteritiveness (Agile-like) with some systems; changes up to last minute Usually get a partner that really knows your business; how its done in multiple jurisdictions Quicker implementation; COTS is more politically attractive; less risk; and less Tremendous amount of resources that an agency simply can’t get any more

Large State Tax Department CIO’s Perspectives (cont’d) Starts with requirements and functional application analysis What is the volume of what we’re looking at? Scope? Functionality? Is what I want to do unique? Can something existing be adapted, such as HR? Agency uses HR system from Cornerstone, benefits of large user base and features, functions of many and get what others do Tax systems very unique and limited vendors; this agency changes systems every year To build software is “very expensive” and often does not achieve full vision Fortunate to have large and talented staff; not the norm in most any other state revenue agencies Agency follows a very prescriptive requirements approach, industry methodologies, very much by the book, even with use of COTS Emphasis on performance evaluation