Scrum Fundamentals: Analyst to ‘Agilist’ By Louis Molnar (C) IAG Consulting 2009 The Agile Business Analyst By: Louis Molnar.

Slides:



Advertisements
Similar presentations
Agile Software Development Robert Moore Senior Developer Curtin University.
Advertisements

Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
SDLC – Beyond the Waterfall
Agile Development Using Scrum Dan Retzlaff Management Information Chief - Applications Development Wisconsin Department of Public Instruction 26 th Annual.
Agile Architecture Prabhu Venkatesan for COMP-684.
Chapter 1: Possess a Clear Understanding of Business Analysis Seven Steps to Mastering Business Analysis (Barbara Carkenord, 2008)
Agile 101.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
Intro to Scrum. What is Scrum? An answer to traditional “fixed cost / strict requirements” contracts which had very high rates of failure Recognizes the.
Agile development By Sam Chamberlain. First a bit of history..
Agile
The Challenge to Survive in Today’s Software Development Environment Evaluating the Agile Methodology.
COMP 350: Object Oriented Analysis and Design Lecture 2
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
CBAP and BABOK Presented to the Albany Capital District Chapter of the IIBA February 3, 2009.
Managing a Project Using an Agile Approach and the PMBOK® Guide
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
An Agile View of Process
Introduction to Agile.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Development Process
5-1 © Prentice Hall, 2007 Chapter 5: Determining Object-Oriented Systems Requirements Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
AgileCamp Presents: Scrum. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution 4.0.
1 Agile Methodology & Programming Ric Holt July 2009.
By Saravanan Bala. General Report 31 % of Software projects are cancelled 75 % of the software projects are considered failures by the people who initiated.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Steve Fastabend Agile Coach Redpoint Technilogies
Business Analysis and Essential Competencies
IIBA - Cedar Rapids Chapter Thursday, Sept. 22, 2011.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.
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.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
1 The Manifesto for Agile Software Development “We are uncovering better ways of developing software by doing it and helping others do it. Through this.
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
CS3100 Software Project Management Agile Approaches.
Het einde van het beroep van tester - Wat Agile, DevOps en Scrum betekenen voor het testvak -
Agile Methodology Paul Mohrbacher. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through.
Jeff Briggs Senior Consultant Capstone Consulting.
Software Engineering (CSI 321) An Agile View of Process 1.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Cultivating Agile Requirements
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Agile Development Implementation Considerations. Agile software development is a methodology based on iterative and incremental development, where requirements.
Using Scrum to Improve Teamwork, Communication, Quality and Speed
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
2 nd Class -Business Cases – Value Proposition -Agile vs. Waterfall Development Process Bus100: Building Software Products: From Strategy to Sales John.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Over Contract negotiation over Processes and tools over Comprehensive documentation overFollowing a plan over.
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!
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Embedded Systems Software Engineering
Flight Software Conference 2016
Agile Training Day 2 November 17, 2015.
Appendix B Agile Methodologies
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Identify the Risk of Not Doing BA
Assist Knowledge Development, Ltd.
Chapter 3: The Project Management Process Groups: A Case Study
Software Engineering (CSI 321)
Agile Software Development
Agile Process: Overview
Scrum Science NGSS: Engineering, Technology, Applications of Science
Appendix B Agile Methodologies
Looking at XP, Scrum, Kanban or Lean
Agile, Scrum and CMMI Methodologies
Presentation transcript:

Scrum Fundamentals: Analyst to ‘Agilist’ By Louis Molnar (C) IAG Consulting 2009 The Agile Business Analyst By: Louis Molnar

2 Learning Objectives © IAG Consulting 2009 Level Set –Agile Manifesto –Mythology IIBA Skill Set Agile BA Traits Inhibitors to Agile Analysis Transition to Agile Coach Growing a More Agile ‘You’

3 Webinar is NOT about Definition/explanation of: Scrum/XP/FDD/Lean, etc Roles within each Agile approach Most of tools/techniques Terminology © IAG Consulting 2009

4 Agile Manifesto Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan © IAG Consulting 2009

5 Mythology Myth #1: We don’t need to follow any development process … Agile Value Statement: “Individuals and interactions over processes and tools” © IAG Consulting 2009

6 Mythology Myth #2: We don’t need to do any documentation … Agile Value Statement: “Working software over comprehensive documentation ” © IAG Consulting 2009

7 Mythology Myth #3: We don’t need any customer sign-off.. Agile Value Statement: “Customer collaboration over contract negotiation ” © IAG Consulting 2009

8 Mythology Myth #4: We don’t need to produce any kind of plan … Agile Value Statement: “Responding to change over following a plan” © IAG Consulting 2009

9 IIBA defines a Business Analyst “A business analyst works as a liaison among stakeholders in order to elicit, analyze, communicate, and validate requirements for changes to business processes, policies, and information systems.” Source: International Institute of Business Analysis (IIBA®)

10 Natural Fit for a Business Analyst? “A business analyst works as a liaison among stakeholders in order to elicit, analyze, communicate, and validate requirements for changes to business processes, policies, and information systems.” The Essential Business Analysis Skills Analyze and understand the business problems Identify and document requirements Communicate effectively (written and spoken) Manage client relationships Facilitate discussions Negotiate and build consensus Model data and processes Plan and manage activities Facilitate and develop business strategy Understand and manage organizational change Source: International Institute of Business Analysis (IIBA®)

11 Agile BA Traits Essential BA Skill Analyze and understand the business problems Measure Your Agility 1)Are you feedback driven? 2)Do you actively seek to learn? 3)Do you adapt your approach to problem solving? 4)Do you explore the problem space?

12 Agile BA Traits Essential BA Skill Identify and document requirements Measure Your Agility 1)Do you continually estimate & prioritize requirements with your stakeholders? 2)Are you quality focused? 3)Are you communications focused? 4)Are you a documentation 'minimalist'?

13 Agile BA Traits Essential BA Skill Communicate effectively (written and spoken) Measure Your Agility 1)Are you communications rich? 2)Are you iterative? 3)Are you using models as a communications vehicle?

14 Agile BA Traits Essential BA Skill Manage client relationships Measure Your Agility 1.Do you integrate Stakeholders into your Team? 2.Are you 'change friendly'? 3.Do you demonstrate ‘servant leadership’ traits.

15 Agile BA Traits Essential BA Skill Facilitate discussions Measure Your Agility 1.Are you a 'facilitator' of discussions? 2.Are you an enabler of groups ‘performing’?

16 Agile BA Traits Essential BA Skill Negotiate and build consensus Measure Your Agility 1)Do you work collaboratively & cooperatively with others? 2)Do you act as a mentor? 3)Are you evolutionary?

17 Agile BA Traits Essential BA Skill Model data and processes Measure Your Agility 1)Are you satisfied with artifacts that are 'just good enough'? 2)Do you use the right model for the right purpose? Activity Diagram Class Diagram Constraint Definition CRC Model Data Flow Diagram Entity Relationship Diagram Process Flow Charts Robustness Diagram Sequence Diagram State Transition Diagram System Use Case UI Prototype User Stories Usage Scenario Use Case Diagram

18 Agile BA Traits Essential BA Skill Plan and manage activities Measure Your Agility 1)Do you assist in the development of the Product backlog that utilize A.G.I.L.E. User Stories? 2)Do you help in the prioritization of the User Stories? 3)Do you assist/map out the release iterations?

19 Agile BA Traits Essential BA Skill Facilitate and develop business strategy Measure Your Agility 1.Do you treat requirements like a prioritized stack? 2.Do you help develop alternate business strategies for the problem domain?

20 Agile BA Traits Essential BA Skill Understand and manage organizational change Measure Your Agility 1.Are you an effective 'assimilator'?

21 Inhibitors to Agile Analysis Viewing agile as a serial or mini-waterfall methodology Focusing on expanding artifacts that you specialize in Focusing on documentation rather than communication Viewing your role as the 'bridge' between the 'business morons' and the 'tech weenies’ Protecting your territory "that's my job" & working to job title Getting stuck in the traditional BA paradigm Developing more documentation than is required Not realizing that models are disposable Having only one-way of doing things Unwilling to experience tasks outside of your comfort zone Not embracing changing requirements & continuous improvement Modeling in isolation Resistance in using collaborative techniques Not accepting & adapting to the fluid nature of the project

22 Transitioning to Agile Coach Develop & foster a productive agile Team Leading by example Educate the Team Over come problems using the PrOpER cycle Build trust Role model

23 Growing a more Agile “You” Covering the basics Share with others Get some training Make a plan Build your network Attend conferences User Groups Find a coach/mentor

24 Recap © IAG Consulting 2009 Level Set –Agile Manifesto –Mythology IIBA Skill Set Agile BA Traits Inhibitors to Agile Analysis Transition to Agile Coach Growing a More Agile ‘You’

25 Objectives 12 Years of living requirements excellence: Completed over 1,200 requirements projects Worked with over 300 of the Fortune 500 companies Trains over 1,200 business analysts annually Somewhat in excess of 700 clients using our methods 50 staff members all 100% focused on excellence in business requirements Annually invested 10% of our revenue in developing our methods, processes and techniques to assure that these are harmonized and industry best practices About IAG Consulting Questions & Answers

26 IAG Agile Scrum: Services 1.Training: 2.Coaching & Mentoring: 3.Scrum Readiness/ Audit Reviews: a. Certified Scrum Product Owner b. Certified ScrumMaster a.Product Owner Coach b.ScrumMaster Coach c.Scrum Implementation Coach a.Readiness Review b.Audit Review © IAG Consulting 2009

27 Garry Senior Vice President Eric Regional Manager IAG Consulting or THANK YOU Important Information Questions & Answers