BA In Transformation 2015 and beyond. Enterprise Challenges High-level thought of BA as Catalyst to solve enterprise challenges Current state of BA role.

Slides:



Advertisements
Similar presentations
Life Science Services and Solutions
Advertisements

Business Architecture
Systems Development Environment
PROGRAM AND PROJECT MANAGEMENT
An Intro to Professionalizing Procurement & Strategic Sourcing
Project Mangement Chapter 4 Framework for Project Management.
NEES Project Management Workshop June 16 June 18 1 Segment 2.
Agile development By Sam Chamberlain. First a bit of history..
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
SYSTEMS DEVELOPMENT Phases, Tools, and Techniques
Fundamentals of Information Systems, Second Edition
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
CHAPTER 9: LEARNING OUTCOMES
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
Certified Business Process Professional (CBPP®)
CBAP and BABOK Presented to the Albany Capital District Chapter of the IIBA February 3, 2009.
This work is licensed under a Creative Commons Attribution 3.0 Unported LicenseCreative Commons Attribution 3.0 Unported License (CC-BY). Project Management.
Kris Hicks-Green April 23, 2013 IIBA Austin
Copyright © 2014 ASTQB Presented by Rex Black, CTAL Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further.
Project Human Resource Management
What is Business Analysis Planning & Monitoring?
UNDERSTANDING VALUE THROUGH VISUAL QUADRANT ANALYSIS BY ELIZABETH BOETTCHER, RED BRICK MARKETING, INC. An Exercise For Small Business Owners.
Integrated PPM Governance Leveraging Org Change Management for PPM Process Implementations Presented by: Allan Mills.
System Analysis and Project Management Key terms and definitions Presentation.
Change Management. Why change management  For many change practitioners, there is no doubt that change management must be used on projects that impact.
BUSINESS ANALYSIS BUSINESS ANALYSIS Toolkit.html.
Developing an IS/IT Strategy
Project Management: Still More Art Than Science Presented By Donald W. Larson AC Bronze, CL June 6, 2007.
Software Project Management Introduction to Project Management.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Establishing a Best Practice Community It Takes a Village to Make a Successful Project Presented by Emily Iem, PMP, CBAP.
Business Analysis and Essential Competencies
The Challenge of IT-Business Alignment
Certificate IV in Project Management Introduction to Project Management Course Number Qualification Code BSB41507.
IIBA - Cedar Rapids Chapter Thursday, Sept. 22, 2011.
Basic of Project and Project Management Presentation.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Team Skill 6: Building the Right System Managing Change (28)
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
Effective Project Management Barbara Stone & Jodie Mathies August 30, 2007.
Science of Nurture 2H Session Two: Identifying Objectives and Target Audiences. Using Buyer Journeys and Personas.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Job Analysis - Competency Modeling MANA 5322 Dr. Jeanne Michalski
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Going beyond business as usual the pci group Integrated Project & Portfolio Management Microsoft Project Server 2003 – ProSight Portfolios Interface Presented.
Introduction to Project Management.  Explain what a project is?  Describe project management.  Understand project management framework.  Discuss the.
Initiation Project Management Minder Chen, Ph.D. CSU Channel Islands
Agile Metrics It’s Not All That Complicated. © 2011 VersionOne 2 Welcome – About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach.
“Business Analysis” Business Analysis Trends in 2015? Prepared By: Tai Tran, CBAP.
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques.
CS223: Software Engineering Lecture 16: The Agile Methodology.
Project Management Enabling Quality Marien de Wilde, PMP April 2007.
F O C U SQ U A L I T YE X P E R I E N C E Why Does a Project Need a Project Manager and a Business Analyst? Similarities, Differences and How They Work.
Building a BA Center of Excellence Gain Momentum...Produce Results!
Beyond the BACoE: Developing Business Analysis Maturity.
Agile Center of Excellence. Richard K Cheng Agile is just a high level concept.
BA vs. SE: What the Heck is a BA
Rapid Launch Workshop ©CC BY-SA.
Systems Analysis and Design in a Changing World, 4th Edition
Agile Training – Agile Overview
Identify the Risk of Not Doing BA
Building a BA Center of Excellence
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Bridging the ITSM Information Gap
Presentation transcript:

BA In Transformation 2015 and beyond

Enterprise Challenges High-level thought of BA as Catalyst to solve enterprise challenges Current state of BA role –What is it –What governs it BA role disruption –Agile –PMI PBA Critical Skills (defining need) –Modeling –Enterprise Analysis –Business Architecture Position Evolution –Professional skills –Being solution architect / trusted advisor –Career path Presentation Agenda

Enterprise Challenges Speed –Rapid pace of disruption and change –Can handle change, lose and lose quickly Productivity –Key to profitability in a slow-growth environment Competitive Advantage –Customer knowledge (internal and external) Product Creation –Three elements of product creation Competitive understanding, organizational capabilities, creating value Growing, Managing and Retaining Knowledge Workers –Generation “Y” dilemma (Millennial)

BA is Catalyst to Face/Conquer these Enterprise Challenges

Position Overview –Enterprise Analysis (business case) Project scope –Process modeling Show how things work now and should work in the future –Requirements Analysis, Elicitation, Management Converting from business (functional/non-functional) requirements to technical (systems) Position Profile –Should act a lot like a Product Manager –Should have solid user knowledge of system, power user –Should be technical enough to “talk the talk” –Much more concerned about outcome than budget or schedule –Should have VERY strong domain knowledge –Must be able to state/represent business case of system/software What is a BA? (industry perspective)

International Institute of Business Analysis (IIBA) – –Started in Canada, now based in Atlanta –11 years old –BA Body of Knowledge (BABOK) Current version 2.0, but moving to 3.0 by early 2015 –Two certifications: Certified Business Analyst Professional (CBAP) Certification of Competency in Business Analysis (CCBA) –New PMI-PBA certification potential impacts Overall –Still in infancy –Doers know it and love it. Companies don’t know what it is or offers –BA position means something slightly different to different organizations –BABOK 3.0 getting a lot of negative feedback Who or What Governs the BA Role?

Important Observation VS. Plan-driven Development Adaptive Development What is Agile??

Transformational way of working Built on a foundation of principles and values –No one-inch-thick rule book From those values and principles come practices –Like daily stand-up, retrospective, story points, etc. Practices are organized into flavors –Agile “flavor” model on next slide Highly extendable – very similar to open source Scrum is to Agile like Red Hat is to Linux Agile in a Nutshell

The Mechanics of Scrum, where does BA fit??

First off, Iterations are work-specific, not role-specific Work specific BA actions include: –Chunk requirements into User Stories –Provide input on need and prioritization of Stories –Write non-functional test cases –Perform non-function tests / acceptance tests –Write specifics –Write documentation / training In Iteration, work focuses on only one aspect of the BA skill set. In Agile a lot of the role is in and around Iteration zero BA Role In Iteration

IIBA (International Institute of Business Analysis) –Sees the BA as a role –Specific function in defining what is going to be done and how it is going to be done Agile (the way of working) –Sees the BA as a skill –Focused around writing and managing requirements and testing output at user interface level How does PMI see BA Work? Is BA Work A Role or a Skill?

Where does software development fit? How do I get what I want from my efforts?

New Project Law: s + s + $ Does Not = Schedule: Scope: Budget: Your Project ‣ Project delivered within the timeframe originally identified ‣ No date slips ‣ Every milestone achieved ‣ Everything originally requested is delivered ‣ Everything delivered works perfectly as the customer requested, no bugs ‣ Did not spend a single cent more than originally estimated to spend ‣ Did not need any additional resources, hardware, etc. throughout entire project on time all scopewithin budget =/ + +=/ happy customer

It seems the focus has been the measurable side of a BA’s responsibilities… –”if it can be measured, it can be monitored and if it can be monitored it is important” –Inside Agile – Way too much focus on requirement breakdown (Stories), Testing and documentation –Outside Agile – Way too much focus on requirements elicitation and development Anecdotal: 95% of people in our classes focus just on the science side of role But missing the growth to becoming a TRUSTED ADVISOR. Enterprise Analysis/Solution Architect/Management Consultant What is this?? BA Role Current Status: Too Much Science Not Enough Art

A.Automation drives productivity and productivity drives profitability B.But Automation screws up processes C.Processes run companies—automate without process redefinition means HUGE WASTE What a BA must do: 1.Build future state, modeling both process and data flow 1.Does it work / will it work ? 2.Drive top / down agreement on new processes and data flow 3.Align requirements to new process 4.Push acceptance of new process flow BA Trends: Models and Analysis

Defining Need –Are there other internal options –Is there a return on investment and what is it –Can the organization do what is requested Basically building the business case Proper Enterprise Analysis drives Executive sponsor behavior –Negotiate need using appropriate analysis techniques on the initial request –Provide leadership to bring disparate executive stakeholders together for informed project initiation Enterprise Analysis isn’t always part of BA’s responsibilities –BA’s in those organizations are given the project initiate and goal and told the model and the solutions and gather the necessary requirements BA Trends: Enterprise Analysis

What is it? –A “blueprint” of the enterprise that provides a common understanding of the organization and is used to align strategic objectives and tactical demands –A bridge between your business model / strategy and how your business functions What does a Business Architect work on? –Supports the definition of business strategy and tactical goas that drive organization operations –Documents business capabilities and primary functions –Develops root cause analysis to review enterprise business problems –Captures an organization view and documents roles, responsibilities, capabilities of business unites TOGAF (The Open Group Architecture Framework) is a community based standards effort to describe methods and tools used by architects BA Trends: Business Architecture

The BA Evolutionary Model “In Project” vs “Out of Project”

Typical SDLC Professional Characteristics –Detailed (accurate) –Black / White (there is a right and wrong way) –Professional not Management Don’t have distraction of staff – No Authority Is seen as unbiased Puts position at a disadvantage when moving to Trusted Advisor / Mgmt. Consultant role What Makes you Successful Can Also Hurt You

Communication skills –Not what you say or write but how it comes across –Sometimes an idea is more important than grammar / spelling / math / specifics –An idea is nothing on less it is communicated Presentation skills –70% image / 30% content –Techniques to engage and stay authentic Negotiation skills –It is NOT about winning / it is about moving forward –It is NOT personal, don’t take it so, it is business Critical Professionals Skills

–Builds solution options Internal or external – find need with sponsors –Drive scope definition –Define future state process Process flows / business rules –Prices / cost definition Deep understanding of internal cost, need and Return requirements –Presents offer –Pass detailed requirements development to “in project” team Trust Advisor / Internal Mgmt. Consultant

BA Career Path

Questions