Business Analysis Training Catalogue IndigoCube by IndigoCube

BUSINESS ANALYSIS Training catalogue

|www.indigocube.co.sa | page

Business Analysis Offerings Transforming the way you and your team perform business analysis is not a one size fits all approach. We understand that your business analysis practice has unique problems and deserves a unique program offering. We will work with your team to identify the pain points that will result in the best opportunity for your team or organisation to realise the change theyâ&#x20AC;&#x2122;re trying to achieve.

We can deliver a course, a webinar, a workshop or provide a coach, but for the same cost, we provide a comprehensive, blended offering. This comprehensive, blended offering aligns the necessary time commitment and the appropriate delivery methods with your specific pain points, goals and team characteristics. We help apply the skills and techniques necessary for success by making sure all training is relevant to your organisation by utilising our tailored offerings to build a program for success. Take a look at what we have to offer and then contact us to get your organisationâ&#x20AC;&#x2122;s unique proposal.

Instructor-led training classes.

Intense workshops focused on a specific issue to enhance business analysis skills or techniques.

Team and individual Sessions to address targeted organisational needs.

|www.indigocube.co.sa | page 2

Certifications and Badges Agile and Analysis Certificates and Badges Our business analysis certification was built with the realization that the role of business analysis is changing and becoming more diverse. Just as roles on development teams are becoming less and less defined, a formal, siloed certification program no longer serves the best interest of organizations, students or the constant evolution of skills needed for success. While our program encompasses the breadth of business analysis, the path to certification is now a personalized experience. Through the incorporation of badges, individuals and organizations can focus their learning experiences on the specializations that directly benefit their unique role/position. In addition to providing flexibility in your achievements, this analysis certification program is supported by Open Badges. Through Open Badges, student accomplishments can be shared through social media and other digital platforms.

Earn Badges and Get Certified Our program is made up of four certification levels and eight badge specializations. As you progress in your certification journey, you will earn badges towards achieving the higher-level certifications. At the core, we believe all analysts, regardless of their environment, project type, or development approach, should possess the foundational skills covered in our Essential Skills for Business Analysis course. This class has been incorporated into our program at all levels.

Certification Levels 1. Agile Analysis Practitioner recognizes an advanced ability to support agile project teams, enable change by defining needs, and ensure valuable solutions. 2. PO Practitioner recognizes the ability to support agile project teams, enable change by defining needs, and ensure valuable solutions as well as effective management of the product backlog. 3. BA Associate recognizes an intermediate ability to enable change and ensure valuable solutions. 4. BA Certified recognizes an advanced ability to enable change and ensure valuable solutions.

|www.indigocube.co.sa | page 3

Badge Specializations Attend 3 of 4 classes:  Agile Analysis  Adopting Scaled Agile Framework  Advanced Agile User Stories  Essential Skills for Business Analysis

- Essential Skills for Business Analysis

Attend these classes:  Developing a Business Analysis Work Plan Skills forfor Business Analysis  Essential Essential Skills Business Analysis



Attend these classes:  Decision Modeling  Essential Essential Skills Business Analysis Skills for for Business Analysis



Attend these classes:  Detailing Business Analysis Data Requirements  Essential Skills for Business Analysis

Attend these classes:  Facilitating a Requirements Workshop  Essential Essential Skills Business Analysis Skills forfor Business Analysis

Attend these classes:  Use Case Modeling and Solution Requirements  Essential Skills for Business Analysis

Attend these classes:  Business Process Analysis  Essential Skills for Business Analysis

|www.indigocube.co.sa | page 4

Agile Transformation Roadmap In today’s IT arena, most organizations are at some stage of an agile transformation. Mature teams are using agile methods as their primary software development lifecycle and have most likely mastered the art of building things right and in short iterations. However, we’ve found that many of these teams still need help building the right thing. Many agile teams are jeopardizing their success by working quickly and not understanding how to incorporate the appropriate amount of analysis to ensure they’re building the right, value driven solution. On the opposite end of the spectrum, other teams are just dipping their toes in the agile pool. For many, the idea of turning a long-term, waterfall project approach into two week sprints is overwhelming. These teams need help determining how they will successfully approach analysis differently – not only in getting over the sprint hurdle, but also the idea of taking team members from a more traditional, role delineated environment to a team based environment.

Agile Transformation Roadmap While this is our standard recommendation, we understand that all agile teams are at a different point in their transformation and created this roadmap for maximum flexibility. Tailor this solution to your specific team needs.

|www.indigocube.co.sa | page 5

Agile Maturity and Optimisation Roadmap for Business Analysts 0. Assess Current State Have you started your agile journey but found that there isn’t a clear beginning, middle or way to measure progress or maturity of your agile transformation? IndigoCube Solution: Agile Team Maturity Assessment Begins with an online assessment and follows up with a feedback consultation with one of our experts. The assessment will provide information related to your AS IS state and allow us to tailor a roadmap for your environment. 1. Level-Set Management & Product Owners Do you have product owners and managers who need to understand a whole new vocabulary, including features, stories, measuring business value, prioritization and MVP (minimum viable product)? Are they overwhelmed or have different interpretations? IndigoCube Solution: Agile Product Owner and Management Overview Course Set expectations and develop an engagement model with the business, product owners and managers. 2. Level-Set Team Does your team have various degrees of agile knowledge or conflicting interpretations? Is inconsistency causing confusion and frustration and undermining the goal of creating a cohesive team? IndigoCube Solution: Agile Team Overview

Get everyone on the same page with agile and the various approaches such as Scrum, Kanban, SAFe. Gain an understanding of not just why these are common practices but how they are relevant to the Agile Manifesto and values. Identify lean, informal just-in-time requirements which help maximize teams’ output and realize the importance of value management and MVP. 3. Experience Agile Success Has your team gone to classes, read books and seen the videos but aren’t able to apply what they’ve learned on their projects and teams? Are they doing all the ceremonies but not getting the benefits they expected from agile? IndigoCube Solution: The Whole Team Approach to Agile Analysis Identify positive and negative behaviors, learn techniques to eliminate unnecessary story points and determine minimum viable product through immersion in a controlled agile environment. 4. Assess Team Skill Gaps Does your team have the collective skills necessary to be successful? IndigoCube Solution: The Whole Team Approach to Agile Analysis One of the outcomes from the workshops in this boot camp is a team activity that assesses each member’s skill level across various domains. The skills assessment inventory highlights gaps and identifies potential development needs.

|www.indigocube.co.sa | page 6

Agile Maturity and Optimisation Roadmap for Business Analysts—- [CONTINUES] 5. Take Agile to the Next Level Is your team proficient at using the user story template but still not building and prioritizing output that has business value or just not ‘acceptable’ based on the necessary requirements? IndigoCube Solution: Advanced Agile User Stories Course Use your real-world projects to take user stories beyond being a placeholder. Identify how to refine, groom, slice and how to ensure your stories satisfy the INVEST characteristics in order to confirm they are ready. 6. Adopt Scaled Agile Have you taken Agile classes and now having trouble making the process work for your organization? IndigoCube Solution: Adopting Scaled Agile Framework (SAFe) Course Address the question, “How much SAFe does your organization need?” Level-set your multi-team framework and identify areas where implementing the framework may be too heavy. 7. Assess Team Progress Are your teams doing self-assessments or retrospectives, but the results are not showing improvement? IndigoCube Solution: Conduct an independent retrospective assessment Many teams fall into the trap of conducting a retrospect and either abandoning agile practices without knowing the impact or adopting agile practices without any real benefit. Therefore, the process improvement is random and not effective. Let our team conduct an independent retrospective assessment and develop a continuous improvement backlog. 8. Validate Metrics Is your leadership looking for metrics that validate and measure your agile practices? Have your teams been successfully doing agile for a while, but showing some signs of fatigue or burnout? Are your teams not sure how to optimize their agile approach or not completely satisfied with their current state of being? IndigoCube Solution: Develop a recognition and reward program, metrics, and key agile success factors Set up an on-going plan to cross functionally train and empower the team members and scrum masters how to define the right metrics based on key agile success factors and values. Regardless of where you team falls, agile needs to be done in a manner that can be sustainable while upholding the spirit of the manifesto and maintaining a healthy, lean cross-functional team environment. Begin your journey to agile maturity using our agile transformation and optimization solution!

|www.indigocube.co.sa | page 7

INDEX Essential Skills for Business Analysis

Business Process Analysis

Detailing Business Data Requirements

Use Case Modelling and Solution Requirements

Developing a Business Analysis Work Plan

Facilitating a Requirements Workshop

Agile Product Owner and Management Overview

Agile Analysis

Agile Team Overview

Advanced Agile User Stories

Adopting Scaled Agile Framework

Improve Communications

Agile Overview

Enterprise Analysis

Decision Modelling Essentials

Defining and Measuring expected Business Value

|www.indigocube.co.sa | page 8

Essential Skills for Business Analysis Overview To identify the best solutions for real business needs, this course provides an extensive inventory of tools and techniques for use in business analysis work. The business analysis skill set includes critical thinking skills, elicitation techniques and requirements analysis and management. Equally important are communication and relationship building skills, whether they be in person or virtual environments. Expertise with analysis tools and techniques becomes even more necessary in today’s fast-paced environment. It is further complicated by the use of dispersed or outsourced teams, complex business processes, time-driven business initiatives, new agile software development approaches, and poorly integrated legacy applications.

Learning Objectives    

  



  

Define business analysis and requirements Elicit requirements from stakeholders using a variety of effective techniques Practice creative thinking skills to engage stakeholders, uncover needs, and identify new approaches and ideas Length: 4 days Compare and contrast analysis techniques in order to select the technique (s) that will most IIBA CDUs: 28 appropriately: Audience:  support your understanding, critical thinking and problem solving This course is designed for  communicate information to stakeholders to enable review and their understanding individuals from any of requirements discipline who are Reduce confusion and development errors by creating excellent requirements that can be performing elicitation easily understood by outsourced or distributed teams activities. Get the most out of your models and diagrams by asking the right questions during Prerequisites: analysis None. Identify why the project is being done (business drivers) in order to ensure the right analysis effort is being performed and so that requirements efforts can be appropriately prioritised Create a context level diagram to identify interfaces, data flows, and high-level processes associated with the project, that is valuable both for planning and communications purposes Apply an approach to manage and record requirements decisions Describe the difference between validating that you’ve built the right solution and verifying that you’ve built the solution right Discuss strategies for content organisation and collaboration, and describe why being more organised increases team agility

Day 1 

Requirements Elicitation and Review  Define business analysis and requirements  Elicit requirement from stakeholders using a variety of effective techniques  Select the most appropriate elicitation technique for the desired results  Use active listening skills to ensure you hear and verify what stakeholders are really trying to say  Learn techniques to review and validate requirements  Practice creative thinking skills to engage stakeholders, uncover needs, and identify new approaches and ideas

|www.indigocube.co.sa | page 9

Essential Skills for Business Analysis [continues] Day 2 

Scope Your Area of Analysis  Identify why the project is being done (business drivers) in order to ensure the right analysis effort is being performed and so that requirements efforts can be appropriately prioritised  Practice an approach to ensure that the problem your project is supposed to address is clearly understood  Analyse and scope the area of analysis, collaboratively with project managers and business stakeholders, to clarify the level and complexity of the business analysis effort needed for the project  Get an introduction to enterprise analysis in order to understand the project in the context of the greater organisation’s strategic goals  Create a context level diagram to identify interfaces, data flows, and high-level processes associated with the project that is valuable both for planning and communications purposes

Day 3 

Requirements Analysis Techniques  Simplify your requirements into four core components that are easier to “consume”  Still writing requirements? Instead, identify the most effective diagramming techniques and modelling options to support your software development approach (waterfall, iterative, and agile) and project type  Compare and contrast analysis techniques in order to select the technique(s) that will most appropriately:  support your understanding, critical thinking and problem solving  communicate information to stakeholders to enable review and their understanding of requirements  Reduce confusion and development errors by creating excellent requirements that can be easily understood by outsourced or distributed teams  Get the most out of your models and diagrams by asking the right questions during analysis.

Day 4 

Applying Business Analysis  Define an approach to conduct effective analysis  Recognise the different levels of requirements and understand why you categorise them  Define excellent requirement characteristics  Describe why requirements are managed for traceability, impact analysis, and reuse  Practice various communication techniques to facilitate productivity and workflow  Discuss strategies for overcoming project obstacles, including lack of stakeholder engagement, conflict resolution, and prioritisation

|www.indigocube.co.sa | page 10

Business Process Analysis Overview Did you know the six costliest words in business are “we’ve always done it that way”? In this class you will learn techniques to help your business look at how things are being done and create solution options to improve the business processes. Creating AS IS and TO BE workflows gives the business analyst a strategic view of business architecture which is essential in Agile, SOA, BPM, and any type of process improvement or COTS project. Workflows are also the foundation for documenting Six Sigma, Lean, and Value Stream process maps. Business process analysis is a fundamental activity in defining changes to existing business systems, business process improvement activities, or performing gap analysis for COTS. It provides the analyst an understanding of the core business processes they can use to suggest alternative solutions which meet core business needs and fit with existing IT infrastructure. Management can then evaluate each alternative for its potential return on investment and the cost of implementation. Every business is searching for better ways of getting work done. Improving efficiency, decreasing costs, increasing productivity and customer service are goals that are universal. Evaluating the business process may result in software changes, procedural changes, organisational changes, personnel changes, etc. The best way to improve business operations is to: 1) study the current procedures, 2) find the core or essential work being done, and 3) define how this essential work will be accomplished. This course teaches a proven approach which gives the business analyst the confidence and credibility to offer and promote the right solution to solve the business problem or opportunity.

outcome 

        

Identify and document complex business process steps in an easy-to-review diagram using industry standard notation BPMN Schedule and conduct discovery/elicitation sessions to learn about current business processes (AS IS) Identify areas for process improvement by reviewing AS IS models Develop process re-design strategies and present them for approval (TO BE) Ask detailed questions to get a complete understanding of business procedures, business rules, information use, and events that impact the business processes Initiate a process modelling effort with clear objectives and an agreed upon goal Define key terms used by the business domain to improve communications within the business Decompose complex processes into lower level tasks and sub-processes Identify the most important business component: Essential Processes Conduct a review of a process model to assure accuracy

Please Note: If students prefer and have experience using MS Visio to draw diagrams, they may bring their laptops with MS Visio to use during some of the workshops. This is not a requirement.

Length: 3 days IIBA CDUs : 21 Audience: This course will be beneficial to any person, in any size organisation, hoping to improve their business processes. The techniques presented can be used without any sophisticated software to quickly identify areas for improvement and fix broken processes. Prerequisites: It is recommended that students first attend our Essential Skills for Business Analysis class or have experience in project scope definition, eliciting requirements, and understanding how process modelling relates to, and is different from, a software development project.

|www.indigocube.co.sa | page 11

Detailing Business Data Requirements Overview Understanding and documenting business data requirements is a critical component in defining complete requirements. Eliciting information needs often uncovers additional processes and business rules. Every business process uses data and almost all business rules are enforced by data. Missing a critical piece of data or incorrectly defining a data element contributes to the majority of maintenance problems and results in systems that do not reflect the business needs. This course teaches students an in-depth approach to data modelling: identifying and defining all necessary data components using both textual templates and an entity relationship diagram. This course teaches business analysis techniques for eliciting, analysing, and documenting data requirements to both new and experienced practitioners. Students will be given data templates with a suggested documentation structure for defining Business Data Requirements.

outcome       

Identify core data requirements beginning with project initiation Identify excellent data requirements at the appropriate level of detail Detail the data requirements (using a data dictionary and data model) Detail complex data-related business rules Assist with the transition of business data to database design Utilise easy normalisation techniques (without all the mathematical theory) Validate data requirements with activity (process or use case) requirements

Even if your organisation has a data administrator or data warehouse team who is responsible for documenting and managing the organisation’s information needs, every project uses a subset of that enterprise information in its own unique way. Business analysts must understand the importance of data in all of their projects and include data requirements in their business requirements documentation. Failing to document which data elements need to be used in a calculation, or displayed on a report, leaves the developer the responsibility of choosing the correct pieces of business data from hundreds if not thousands of available fields. These missing requirements often lead to expensive and lengthy project delays during the testing phase.

Length: 3 days IIBA CDUs : 21 Audience: This course is designed for business analysts, systems analysts, data administrators, database administrators, or any other project team member involved with business analysis. Prerequisites: It is recommended that students first attend our Essential Skills for Business Analysis class or have experience in project scope definition, eliciting requirements from subject matter experts, and understand how business requirements fit into the entire systems development effort.

|www.indigocube.co.sa | page 12

Use Case Modelling & Solutions Requirements Overview Use case modelling is a commonly used analysis technique which results in functional requirements and a framework for test case development. When the solution to a business problem or opportunity involves a software component, the solution team must determine how software will best support the business. This class focuses on the business analysis work which includes defining functional, non-functional, and transition requirements which describe the solution and roll out needs. Specifically techniques for communicating the business requirements to the solution team, tracing each business requirement to the supporting solution component, assessing the solution applicability and planning for a smooth transition to the solution. Mentor-led workshops require students to practice the techniques as they learn. Students are encouraged to bring their own projects to class.

outcome       

Use business requirements to identify, evaluate and present alternative design solutions Length: 3 days IIBA CDUs : 21 which meet customer needs Audience: Prioritise requirements for inclusion in the software development phase using This course is designed for plan-driven (traditional) and change-driven (iterative and agile) techniques business analysts, systems Elicit analyse, and communicate functional requirements that specify how users analysts, or any other project team members will interact with the software and how the software will respond responsible for developing Deliver consistent, detailed use case descriptions functional, non-functional, Incorporate usability principles when developing prototypes and transition Identify non-functional requirements appropriate for each project requirements. Students are Learn to assess organisational readiness and build a transition or rollout plan to smooth the encouraged to bring examples of their implementation of new software for the business

requirements documents to the class for review and feedback. This course may also be appropriate for individuals who manage business analysts. Developers and solution implementers will benefit from an understanding of how functional and non-functional requirements are elicited and analysed. Prerequisites: It is recommended that students first attend our Essential Skills for Business Analysis class or have experience in project scope definition, eliciting requirements from stakeholders, and understanding how business requirements fit into the entire systems development effort. It is also recommended that students attend Business Process Analysis before attending this class.

|www.indigocube.co.sa | page 13

Developing a Business Analysis Work Plan Overview Having trouble getting started with your business analysis work? Unsure about how much time to request from your project manager? Developing a business analysis work plan will prevent major problems by ensuring that all of the appropriate stakeholders are involved and the requirements will be analysed and presented using the most effective communication approaches. This class teaches students to consider all of the project and stakeholder characteristics before deciding on appropriate deliverables and producing a time estimate. The work plan also helps the business analyst develop realistic time estimates based on the chosen deliverables. These estimates provide detailed justification for negotiation with project managers and project sponsors. During class students are presented the Business Analysis Planning Frameworkâ&#x201E;˘ and are given worksheets to guide their planning efforts.

Students are encouraged to bring their own project initiation documentation for a current or past project to the class. During the workshops, students will develop their business analysis work plan. If students do not have a project, a class case study is available and should be reviewed prior to the first day of class. Regardless of when the BA joins a project or the project type, this class will guide planners to deliver an intelligent business analysis work plan to the project manager and have a detailed roadmap upon which they can immediately begin to execute. The business analysis work plan may be a single sheet of brief notes on a small project or a more formal document on larger projects. Regardless of the output produced, an excellent business analyst thinks through the plan before starting work.

Length: 3 days IIBA CDUs: 21 Audience: This course is intended for anyone who is interested in learning a practical approach to planning the necessary tasks for their project. Prerequisites: Business analysts registering for this course must have attended Essential Skills for Business Analysis, or have at least 2 yearsâ&#x20AC;&#x2122; experience in requirements elicitation, analysis and documentation using structured techniques.

|www.indigocube.co.sa | page 14

Facilitating a Requirements Workshop Overview The art of bringing people together, face-to-face or remotely, to elicit requirements and gain consensus on solutions is a critical success factor for all business analysis professionals. This course teaches facilitation techniques that can be used for structured sessions and “facilitation-on-the-fly.” This course goes beyond traditional facilitation training by focusing on facilitation techniques specific to eliciting business and functional requirements. This class is limited to 8 students, allowing each student the opportunity to practice facilitating multiple requirements sessions in a “safe” environment with personalised feedback. Students will spend 60% of class time participating in interactive, real-world business case studies and performing each key role in at least one session. The workshops in this course require students to plan the requirements eliciting session, develop the correct questions to ask the group, and facilitate the group to a consensus on the requirements using one of the learned techniques. Students will conduct a requirements workshop for at least one requirement deliverable (i.e. context level dataflow diagram, workflow diagram).

outcome           

Facilitate using proven techniques for eliciting detailed business, functional and non-functional requirements Identify when and how to use each technique Develop confidence and a skill set to conduct requirements workshops Actively practice learned skills and techniques Use a requirements planning session template Prepare the participants for the requirements session Perform each facilitation role through role playing each session Conduct the session to stay focused on the core requirement that was planned as a deliverable Select which facilitation technique to use for each core requirement being elicited Complete checklists for managing and conducting the session Facilitate a requirements workshop

Length: 3 days IIBA CDUs: 21 Audience: This course is designed for experienced, knowledgeable business analysts or project managers involved with requirements elicitation and analysis. Students are expected to understand the purpose of business and functional requirements. Prerequisites: It is recommended that students first attend our Essential Skills for Business Analysis class or have experience in project scope definition, eliciting requirements from subject matter experts, and understanding how business requirements fit into the entire systems development effort.

|www.indigocube.co.sa | page 15

Agile Product Owner and Management Overview As the key stakeholder, the agile product owner role is very hands-on and a significant role that can make or break an agile team. The management team (including project management, resource management and upper management) must change and adjust their approaches to alignwithagilevalues. In order to take full advantage of agile, the organization must have a program and portfolio framework that is just as mature as the teams’ agile mindset. Everyone involved with an agile project needs to have an understanding of the needs they are trying to satisfy and the approach they are using to satisfy those needs. This course is designed to introduce product owners and management to the agile values, principles, and techniques, as well as an overview of various agile approaches (Scrum, Kanban), the Scaled Agile Framework (SAFe) and value management.

Learning Objectives 

Review the concepts of agile and discuss the impacts to the organization



Understand the agile product owner’s role in an agile environment and the benefit in creating a subject matter expert support team



Learn an approach to determining Minimum Viable Product and ROI



Understand a featured driven approach to value management



Suggestions for creating healthy and sustainable agile teams Identify ways to change actions, behaviours, and results to drive agile values



Length: 1 day IIBA CDUs: 7 Audience: This course is designed for product owners and management involved with agile teams who need a more in-depth understanding of the process and skill set needed for a successful agile team. Prerequisites: None.

|www.indigocube.co.sa | page 16

Agile Analysis Overview Agile teams and organisations find out sooner or later, that with agile, building the wrong things faster is very possible if you leave out a key component: understanding the real problem and evaluating the impact of the potential solution before going off and doing your sprint as fast as you can. Our goal is to provide agile analysis approaches and techniques for your team to ensure the right thing is built, have user stories that clearly identify the minimum viable product, and potentially eliminate unnecessary stories. The course provides practical guidance on handling complex projects, spontaneous scenarios and decision points that occur on an agile project. Our material covers many variations of agile so that each analysis technique taught can be adapted to different types of projects, different types of agile teams, and even a variety of agile frameworks.

Class Experience An emersion learning approach, along with role playing, allows students to practice the techniques as they learn. Students will experience what a project that is fully leveraging agile Length: 3 days concepts and culture looks and feels like. This allows them to better understand their role on IIBA CDUs: 21 the team and appreciate their team member’s contributions. During the course, we will Audience: demonstrate how analysis is used at every step in the process, even if the techniques are not This course is designed for always recognized as analysis in their current environment. anyone working on an agile

This course includes many of the concepts found in the Scaled Agile Framework (SAFe), as team, but is especially well as Scrum and Kanban. It supports the standards outlined in the IIBA BABOK® Guide V3. helpful for product owners, This course will also touch upon alternate agile approaches (XP, Iterative, DAD, hybrids such business analysts, systems as Scrumban, Scrumfall and other organic approaches) to allow those pursuing agile to analysts, or any other team consider all the practices and options. Students who have previously take our Essential Skills member involved with for Business Analysis will see how to leverage and reuse those skills in an agile environment. requirements on an agile

Pre- and Post-Class Reinforcement There is a short pre-requisite quiz for students to help tailor the learning process. To ensure the knowledge gained during class is transferred to actionable plans, we include an optional comprehensive quiz after class along with our Make Learning Stick program. Students are encouraged to bring projects into class for exercises and to develop a more personalised post -class action plan to take their project to the next step.

Learning Objectives       

  

Practice Scrum, release, and iteration/sprint planning sessions through mock exercises Understand how the different agile environments (Scrum, SAFe, Kanban) impact roles, planning, and ceremonies Review the top-down hierarchy of managing value Align scoping and analysis techniques with each stage and step in the agile framework Understand how to best facilitate communication among the agile team (i.e. the product owner, the domain stakeholders, the development team) Perform team skills gap analysis to help the team become even more effective and responsive to changes Develop user stories using the 3Cs, the features, the epics, and cross-functional supporting content (ie: acceptance test, examples, models) for the purposes of building the right solution and tracing value Discuss other types of backlog items including non-functional requirements, spikes, technical debt, and impediments Elicit and communicate the appropriate level of requirement detail and how to use “just in time” practices for delivering the details Outline the role analysis plays in managing, estimating, and prioritizing the backlog, along with designing, building, and testing activities. Copyright IndigoCube

project. This course may also be appropriate for individuals who manage individuals working on an agile team and need a more in‐depth understanding of the process and skill set useful for an agile team. Prerequisites: None.

|www.indigocube.co.sa | page 17

Agile Team Overview Overview This course is designed to introduce students to the agile values, principles, and techniques and takes an in-depth look into the skills necessary to ensure that the team is identifying and delivering the right thing. Whether you’re an existing agile team or new to an agile approach, everyone involved with an agile project needs to understand the needs they are trying to satisfy and the approach they are using to satisfy those needs. It is an excellent class to level-set management, product owners, or others working in an agile environment.

Learning Objectives    

How agile values and principles guide a team’s approach to delivering the right thing Determine who should fill common agile roles Understand common agile approaches and how to apply to the learner’s situation Apply agile techniques such as discovery and delivery boards, relative estimating, iteration planning, and others.

Length: 1 day IIBA CDUs: 7 Audience: This course is designed for anyone working on an agile team, but is especially helpful for product owners, business analysts, systems analysts, or any other team member involved with requirements on an agile project. This course may also be appropriate for individuals who manage individuals working on an agile team and need a more in-depth understanding of the process and skill set useful for an agile team. Prerequisites: None.

|www.indigocube.co.sa | page 18

Advanced Agile User Stories Overview Slicing user stories down to fit into sprints is a key component of agile. The user stories are intended to be small and at the same time they should provide just enough and just in time requirements. Without the correct level of acceptance criteria, agile teams may find themselves building things fast, but not necessarily building the right things. Teams often struggle with these agile concepts and ways of identifying the necessary requirements while still adhering to lean documentation. This class is intended for an agile team to improve their user stories relating to prioritization, estimation, splitting stories, organizing, and making sure that they are refined and ready for the development sprints. This includes breaking them down from epic to feature to stories and eliciting the acceptance criteria.

Participants should bring their initiative or epic to break down into user stories or they can use a case study provided.

Learning Objectives       

Provide practical tools and techniques to ensure your User Stories meet the characteristics of INVEST Utilize the core component analysis approach to ensure that a cohesive set of user stories exist Take user stories from their raw state to refine them into a ready state Understand the capturing of acceptance criteria; examples and scenarios Identify how to triage change requests and determine where they fit in the backlog Review and create traceability of stories to their features and to their initiative or epic to ensure that the context of the project is defined Define and assign business value to prioritize and help manage minimal viable product discussions.

Length: 2 days IIBA CDUs: # Audience: This course is designed for product owners and management involved with agile teams who need a more in-depth understanding of the process and skill set useful for an agile team. Prerequisites: We recommend participants have attended our “The Whole Team Approach to Agile Analysis“ course or have equivalent agile experience or training.

|www.indigocube.co.sa | page 19

Adopting Scaled Agile Framework (SAFe) Overview In this course, we will level-set your multi-team framework and identify areas where implementing the framework may be too heavy. Then we will work through intensive case studies to apply SAFe concepts and identify healthy habits in a scaled agile culture. During these case study activities, we will address your issues as we walk through the team, program, and portfolio level activities.   

You’ve taken an introduction to SAFe class. You’ve started implementing SAFe. One of your team members has been SAFe certified.

Regardless of where you are in the implementation process, you need to make the process work for your organization. The beauty of agile is its flexibility and focus on lean processes and the concept of “just enough”. This core concept doesn’t need to be forgotten when scaling agile in your organization. This course will answer the question, “How much SAFe does your organization need?” Learning how to go agile and do analysis in agile is one thing (hopefully, you took our Agile Analysis Boot Camp), but scaling agile in a medium to large organization is another effort entirely. As simple as the agile methodology wants to be, it can get complicated when you bring multiple teams into the mix. The Scaled Agile Framework (SAFe) is a specific approach to scaling and structuring agile by helping teams manage dependencies and risk through coordination and communication at the program and portfolio level.

Learning Objectives 

  

      

Understand how different agile environments impact roles, planning, and ceremonies for SAFe Review the top-down hierarchy of managing value with emphasis on the portfolio and program Align analysis techniques with each stage and step in the SAFe framework Understand how to best facilitate communication among the SAFe stakeholders (i.e. portfolio managers, product managers, product owners, scrum masters, special services, release managers) Develop portfolio initiatives, epics, themes, features, and capabilities for the purposes of building the right solution and tracing value Apply elicitation and analysis to help make the best decisions at the portfolio and program level Outline the role analysis plays in managing, estimating, and prioritizing the portfolio and release plan Identify and negotiate the factors associated with ready and done Practice portfolio and release planning using case studies and mock exercises Effectively establish a triage approach to manage the flow of new initiatives Identify how a portfolio or program level analyst helps manage changing needs.

Length: 2 days IIBA CDUs: 14 Audience: This course was developed for students with a foundational knowledge of agile and SAFe processes and principles. We recommend this course for anyone working in a scaled agile environment, but it is especially helpful for product owners, business analysts, product managers, scrum masters, architects, shared services managers, project managers, program managers, PMO managers, initiative/epic owners, DevOps managers, systems analysts, or any other team member involved with the planning of an agile project. Prerequisites: None.

|www.indigocube.co.sa | page 20

Improve Communication Overview This highly interactive and fun programme focuses on improving communication through improvisation lessons that will help you be a more attentive and flexible team member. You will walk away with lessons to help you stay in the present, temporarily suspend judgment, keep conversations moving forward and listen generously. These skills are needed to build positive, trust based, results oriented teams.

Outcome        

The learning objectives for this programme includes: Improve individual and team effectiveness through enhanced verbal communication skills Learn to think on your feet and keep a conversation moving forward Strengthen your preverbal communication abilities Improve active listing ability Master different types of questions using various questioning techniques Participate in teamwork activities to be a real team player Learn lessons that will help you be an advocate for your stakeholders

Course Outline Day 1 



Thinking on you feet  Understand verbal Communication  Communication is more than just words  Why we communicate  How we communicate  Communication process Communicate with impact  Removing barriers to communication  Improve communication through improvisation Communication Techniques  Requirements Communication  Crucial Conversation  Giving and receiving feedback  “Canons of Construction” – no room for interpretation  Conflict resolution Communicate Skilfully  Stay in the present  Move the conversation forward  Suspend judgement

Length: 3 days IIBA CDUs: 0 Audience: All staff on various levels in the organisation. Prerequisites: None.

|www.indigocube.co.sa | page 21

Improve Communication [continues] Day 2

Day 3

 Active listening  Thinking Environment  Create the space to keep the



Teamwork / Collaboration  Characteristics of Self Organised teams  Communication that encourages collaboration in teams  Teamwork or Collaboration  Cross organisational collaboration  Building Consensus and cohesion



Solving problems as a team  Route Cause Analysis  The Six Thinking Hats  Building Consensus and cohesion



Building a collaborative team environment



conversation moving Ten Component of Listening



Transformative Listening  Remove listening barriers  Listen to understand then to be understood



Active listening Techniques  Gaining understanding techniques  Create meaning and flow through dialogue  Improve through improvisation



Non-verbal Communication  Body Movements  Movement  Stance and posture  Do and don’t



Personal Appearance  First Impressions  Dress Code  Colour Psychology Preverbal  How we say it is more important than what we say  Impact of your voice  Improve through improvisation Questioning types and techniques  Advantage of having good questioning skills  Characteristic of a good questioner  Questioning types and techniques



|www.indigocube.co.sa | page 22

Agile Overview Overview An increasing number of organisations have found agile software development approaches help them develop products or systems much more effectively than in the past. The values, principles, and techniques of agile approaches certainly help teams build things right. This course is designed to introduce students to the agile values, principles, and techniques and takes an in-depth look into the skills necessary to ensure that the team is identifying and delivering the right thing. Whether you’re an existing agile team or new to an agile approach, everyone involved with an agile project needs to understand the needs they are trying to satisfy and the approach they are using to satisfy those needs. Students will gain knowledge and skills by practicing techniques and soft skills needed to operate effectively in an agile environment. Interactive workshops allow students to practice the techniques as they learn. This course is aligned with Scaled Agile Framework (SAFe) version 3.0, supports the standards outlined in the IIBA BABOK® Guide V2.0 and supports the Learning Objectives of the ICAgile Value Management Track. This course can be taken either stand-alone or as part of the broader Analysis in Agile Curriculum.

outcome    

Length: 1 day IIBA CDUs: 0 Audience: This course is designed for anyone working on an agile team, but is especially helpful for product owners, business analysts, systems analysts, or any other team member involved with requirements on an agile project. This course may also be appropriate for individuals who manage individuals working on an agile team and need a more in-depth understanding of the process and skill set useful for an agile team. Prerequisites: None.

|www.indigocube.co.sa | page 23

Enterprise Analysis Course Outline Day 1 

Developing an Effective Business Case  What is a business case?  Understanding your audience  Where does the business case fit into a product / project life cycle  Learn an effective framework for a business case  Defining and Presenting the Case  Learn how to write an effective executive summary  Learn the components of a detailed mission statement  Project initiative  Strategic Alignment  One project vs multiple projects or program to achieve mission  SMART objectives and key performance indicators  Define approach used for analysis  Justifying the Case  Identification and prioritisation of alternative solutions  Cost / benefit analysis  Terminology and financial metrics  Estimating techniques  Process-related impacts  People-related impacts  System-related impacts  Quantifying Implementation costs  Quantifying Ongoing/operating costs  Quantifying Benefits  Documenting the Case  How much detailed is required  Which assumptions should be documented  Documenting known Risks  Develop your action Plan/Course Summary  Develop your action plan to improve your business case  Student questions/discussion topics

Length: 3 days IIBA CDUs: 21 Audience: This course is designed for business analysts, product owners, project managers, program or portfolio managers or any other business partner or project team member involved with developing and writing a business case. This course may also be appropriate for individuals who manage business analysts and need a more in-depth understanding of the process and skill set that would be helpful for effective business analysis. Prerequisites: This is an advanced topic that expands upon elements presented in our foundation and core analysis classes. We recommend students first attend our Essential Skills for Business Analysis class (or Virtual sub-sets on Requirements Analysis Techniques and Scope Your Area of Analysis), as well as our Business Process Analysis course; or have equivalent experience.

|www.indigocube.co.sa | page 24

Enterprise Analysis [continue] Course Outline Day 2 & 3 KPIs for Success: Problem Solving and Impact Analysis Key Performance Indicators (KPIs). The two critical components of a great concept or solution proposal are (1) a well-articulated problem that’s important to solve, and (2) a valuable solution that will provide compelling benefits to its audience and to the business. However, it’s not enough to simply state those two components when pitching a proposal or creating a business case — they must be substantiated through effective business analysis.

Outcome  

 



Analyse, define, size and justify the importance of solving (or ignoring) a particular problem Identify considerations for analysing and sizing a potential business solution or opportunity, including important stakeholder characteristics and an effective comparison of the potential solution to the problem size Develop a sound solution position statement that clearly describes intended business value and outcomes designed for success Define Key Performance Indicators, measures and requirements for solution success and benefit delivery; describe how this information supports effective program design, project scoping and planning to maximise benefits delivery Identify potential risks to achieving critical solution results, describe the different risk responses and planning strategies, such as mitigation and contingency plans, and identify key considerations for ensuring solution success

|www.indigocube.co.sa | page 25

Decision Modelling Essentials Overview The Decision Model provides an efficient new method of eliciting, organising, managing and testing business rules and logic. It brings to the world of business rules and logic a well-defined structure with the rigor of integrity and normalisation principles. The model supports business rule analysis and decision analysis techniques as defined in the BABOK®. It is similar in concept to what the relational model brings to the world of data and it provides business analysts with a new way to succeed by ensuring that critical business rules are not missed. The Decision Model provides for unambiguous creation and sustainable maintenance of business logic, often with minimal IT intervention. This course introduces business analysts to The Decision Model and provides a practical step- by-step approach for creating them as a new standard business analysis deliverable. It is based on the book, The Decision Model: A Business Logic Framework Linking Business and Technology by Barbara von Halle and Larry Goldberg (Taylor & Francis, LLC, 2009). This course provides ways to improve and simplify business process models as well as an approach to decomposing business policies, rules, and related statements into reusable pieces of business logic. This model is also an important artifact for improving data quality and supports compliance with regulations such as Sarbanes-Oxley.

Length: 2 days IIBA CDUs: 14 Audience:

The first day of the course covers concepts and principles with reinforcing exercises. It This course is designed for continues to the second day with an in-depth case study where attendees work to apply business analysts, decision modelling techniques to a realistic, sophisticated business situation. Exercises and business stakeholders, workshops can be done with paper and pencil. Students will have access to downloadable business stewards, project decision modelling templates for use after class. managers, system and

outcome         

Create The Decision Model which provides a simplistic business friendly view of complex business rules Understand when and how to utilise The Decision Model Show how The Decision Model simplifies Business Processes Models Prioritise business decisions based on business impact Explain to business and technical audiences the benefits and concepts of The Decision Model as a new kind of deliverable Discuss the important differences between The Decision Model and previous techniques Build skeletal and detailed decision models Conduct validation of decision models against integrity principles Encourage business creativity in discovering optimum decision model content Conduct decision modelling sessions in an iterative fashion

enterprise architects involved with elicitation, management, and/or automation of business rules and logic. Prerequisites: Students should understand the concepts of workflow modelling.

|www.indigocube.co.sa | page 26

Defining and Measuring expected Business Value Overview Business leaders and managers who evaluate proposals are faced with the challenge of selecting the most valuable investments for their organizations. They must select problems that are important to solve and that will provide compelling benefits. However, it’s not enough to simply state those two components when pitching a proposal or creating a business case – they must be substantiated through effective business analysis. Critical thinking must be applied to determine whether the stated problem is a problem and whether the benefits of that solution are sufficient given the investment that is required. Thorough analysis is then required to create the “right” solution – a solution uniquely designed to solve the problem and capture the expected business value. This course provides frameworks and techniques to help students analyse the business situation and select the best solution. It includes lessons on developing the right KPIs so students can architect and measure success for any solution they propose. Interactive workshops allow students to practice the techniques as they learn using case studies as well as their own projects. Length: 2 days

Outcome      

 

Analyse, define, and size a particular problem or opportunity Identify the importance and value of solving (or ignoring) the problem or opportunity Develop a sound solution position statement that clearly describes intended business value and outcomes needed for success Recommend a solution option that delivers the desired outcome and value Establish measures for solution success and benefit delivery Choose “key” measures (KPIs) and describe how this information supports effective program design, project scoping and planning to maximize benefits delivery Identify potential risks to achieving critical solution results and describe the different risk responses and planning strategies, such as mitigation and contingency plans Perform cost benefit analysis and develop a business case to support solution recommendations

Course Outline      

IIBA CDUs: 14

Understand the importance of measuring the success of your business Envision Business Success Describe Solution Option Success Plan for Performance Success Communicate Business Value Course Summary

Audience: This course is designed for more experienced or senior business analysts, product managers, product owners, project, program or portfolio managers or any other business partner or project team member involved in problem resolution, impact analysis, proposal, business case or value proposition development, as well as program or project scoping. Prerequisites: We recommend students first attend our Essential Skills for Business Analysis class (or Virtual sub-sets on Requirements Analysis Techniques and Scope Your Area of Analysis), as well as our Business Process Analysis course; or have equivalent

|www.indigocube.co.sa | page 27

|www.indigocube.co.sa | page 28