27 Agile Business Analyst courses in Bristol

Agile Release Plans: In-House Training While many Agile frameworks provide guidance on a focus on value and iterative development, many do not explain how that value is delivered to the customer. Release Plans have become an accepted and common practice to bridge the gap between the Product Vision and the Product Backlog (Agile requirements). In this course, you will be provided with an introduction to Agile and to Scrum, the most utilized Agile framework. You will also learn how the Vision, Roadmap, and Charter help to establish the Release Plan. The goal of this course is to equip you with the necessary knowledge, skills, and techniques to build Release Plans to ensure you deliver the most value to your customers. What you will Learn At the end of this program, you will be able to: Recall the Scrum framework elements (roles, events, and artifacts) Examine the benefits of Agile Develop a Product Vision and Roadmap Create an Agile Project Charter Prepare a Release Plan Write user stories to support a Product Backlog Foundation Concepts Introduction to Scrum Scrum Overview Agile Benefits Product Definition Business Goals Product Vision Product Roadmap Agile Project Charter Product Scope Project Risks Release Deadlines Sprint Durations Team Norms Release Planning Release Plan Process Select Stories and a Release Date Product Backlog User stories Building the product backlog Product Backlog Refinement Transitioning to the Scrum Team

Assuring Quality Through Acceptance Testing: In-House Training It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. It is the business analyst's job to define the business problem to be solved by IT. It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. The business analyst is not only concerned with the testing itself, but also with the management and monitoring of the users doing the acceptance testing, and recording, analyzing, and evaluating the results. What you will Learn Upon completion, participants will be able to: Create a set of acceptance test cases Manage and monitor an acceptance test stage where users perform the testing Work with the development team in the systems testing stage Assess the solution once it is in the business environment Foundation Concepts The role of the business analyst An introduction to the BABOK® Guide BA roles and relationships through the project life cycle Introduction to assuring software quality through acceptance testing The Scope of IT Testing Overview of testing stages The testing process Testing documentation Pre-Acceptance Testing The BA's role in testing Early development testing stages (unit and integration) Late development testing stage (system) The Acceptance Test Stage - Part I (Planning, Design, and Development) Overview of user acceptance testing Acceptance test planning Designing user acceptance tests Developing individual user acceptance test cases Building effective user acceptance test scenarios The Acceptance Test Stage - Part II (Execution and Reporting) Operating guidelines Execution Reporting Post-Acceptance Testing Overview Project implementation Project transition (project closure) Production through retirement Testing Commercial Off-the-Shelf (COTS) Software Overview Selecting the software Implementing the software Summary What did we learn and how can we implement this in our work environments?

Use Cases for Business Analysis: In-House Training The use case is a method for documenting the interactions between the user of a system and the system itself. Use cases have been in the software development lexicon for over twenty years, ever since it was introduced by Ivar Jacobson in the late 1980s. They were originally intended as aids to software design in object-oriented approaches. However, the method is now used throughout the Solution Development Life Cycle from elicitation through to specifying test cases, and is even applied to software development that is not object oriented. This course identifies how business analysts can apply use cases to the processes of defining the problem domain through elicitation, analyzing the problem, defining the solution, and confirming the validity and usability of the solution. What you will Learn You'll learn how to: Apply the use case method to define the problem domain and discover the conditions that need improvement in a business process Employ use cases in the analysis of requirements and information to create a solution to the business problem Translate use cases into requirements Getting Started Introductions Course structure Course goals and objectives Foundation Concepts Overview of use case modeling What is a use case model? The 'how and why' of use cases When to perform use case modeling Where use cases fit into the solution life cycle Use cases in the problem domain Use cases in the solution domain Use case strengths and weaknesses Use case variations Use case driven development Use case lexicon Use cases Actors and roles Associations Goals Boundaries Use cases though the life cycle Use cases in the life cycle Managing requirements with use cases The life cycle is use case driven Elicitation with Use Cases Overview of the basic mechanics and vocabulary of use cases Apply methods of use case elicitation to define the problem domain, or 'as is' process Use case diagrams Why diagram? Partitioning the domain Use case diagramming guidelines How to employ use case diagrams in elicitation Guidelines for use case elicitation sessions Eliciting the problem domain Use case descriptions Use case generic description template Alternative templates Elements Pre and post conditions Main Success Scenario The conversation Alternate paths Exception paths Writing good use case descriptions Eliciting the detailed workflow with use case descriptions Additional information about use cases Analyzing Requirements with Use Cases Use case analysis on existing requirements Confirming and validating requirements with use cases Confirming and validating information with use cases Defining the actors and use cases in a set of requirements Creating the scenarios Essential (requirements) use case Use case level of detail Use Case Analysis Techniques Generalization and Specialization When to use generalization or specialization Generalization and specialization of actors Generalization and specialization of use cases Examples Associating generalizations Subtleties and guidelines Use Case Extensions The <> association The <> association Applying the extensions Incorporating extension points into use case descriptions Why use these extensions? Extensions or separate use cases Guidelines for extensions Applying use case extensions Patterns and anomalies o Redundant actors Linking hierarchies Granularity issues Non-user interface use cases Quality considerations Use case modeling errors to avoid Evaluating use case descriptions Use case quality checklist Relationship between Use Cases and Business Requirements Creating a Requirements Specification from Use Cases Flowing the conversation into requirements Mapping to functional specifications Adding non-functional requirements Relating use cases to other artifacts Wire diagrams and user interface specifications Tying use cases to test cases and scenarios Project plans and project schedules Relationship between Use Cases and Functional Specifications System use cases Reviewing business use cases Balancing use cases Use case realizations Expanding and explaining complexity Activity diagrams State Machine diagrams Sequence diagrams Activity Diagrams Applying what we know Extension points Use case chaining Identifying decision points Use Case Good Practices The documentation trail for use cases Use case re-use Use case checklist Summary What did we learn, and how can we implement this in our work environment?

Leading SAFe®: In-House Training During this course, attendees gain the knowledge necessary to lead a Lean-Agile enterprise by using the Scaled Agile Framework® (SAFe®) and its underlying principles derived from Lean, systems thinking, Agile development, product development flow, and DevOps. Participants in the class gain insights into mastering business agility to thrive in competitive markets. They discuss how to establish team and technical agility and organize and re-organize around the flow of value. Attendees also learn and practice the skills to support and execute PI Planning events and coordinate multiple Agile Release Trains (ARTs). Class participants will explore the importance of adopting a customer-centric mindset and Design-Thinking approach to Agile Product Delivery. Learners will also understand how to implement a Lean Portfolio Management function within their enterprise. What you will Learn After attending this class, attendees should be able to: Lead the transformation to business agility with SAFe® Become a Lean-Agile leader Understand customer needs Design Thinking Enable Agile Product delivery Implement Lean Portfolio Management Thrive in the digital age with business agility Become a Lean-Agile leader Establish Team and Technical Agility Build solutions with Agile Product Delivery Explore Lean Portfolio Management Lead the change Become a Certified SAFe® Agilist

SAFe® for Government: In-House Training Transitioning to Lean-Agile practices for building technology-based capabilities is especially challenging in the government context. But issues of legacy governance, contracting, and organizational barriers can be overcome with the right information and strategies. During this course, attendees will learn the principles and practices of the Scaled Agile Framework® (SAFe®), how to execute and release value through Agile Release Trains, and what it means to lead a Lean-Agile transformation of a program inside a government agency. Attendees gain an understanding of the Lean-Agile mindset and why it's an essential foundation for transformation. They'll also get practical advice on building high-performing, multi-vendor Agile teams and programs, managing technology investments in Lean flow, acquiring solutions with Agile contracting, launching the program, and planning and delivering value using SAFe®. Attendees also learn how specific leadership behaviors can drive successful organizational change in government. What you will Learn To perform the role of a SAFe® for Government leader, you should be able to: Transition government programs from traditional software and systems development models to Lean-Agile and DevOps mindsets, principles, and practices using SAFe® Adapt technology strategy, budgeting and forecasting, acquisition, compliance, and governance processes to flow-based practices using emerging government guidelines Organize government programs into one or more Agile Release Trains (ARTs) and execute in Program Increments (PIs) Explore Large Solution coordination in a government and multi-vendor environment Identify and internalize the mindset and leader behaviors essential to successful Lean-Agile transformation Follow success patterns for SAFe® implementations adapted to the government context Build a preliminary outline of next steps to begin and / or accelerate the SAFe® implementation in your program or agency Advancing Lean-Agile in government Embracing a Lean-Agile mindset Understanding SAFe® Principles Creating high-performing Agile teams and programs Planning with cadence and synchronization Delivering value in Program Increments Mapping the path to agency and program agility Leading successful change

Effecting Business Process Improvement: In-House Training Business analysts facilitate the solution of business problems. The solutions are put into practice as changes to the way people perform in their organizations and the tools they use. The business analyst is a change agent who must understand the basic principles of quality management. This course covers the key role that business analysts play in organizational change management. What you will Learn You will learn how to: Define and document a business process Work with various business modeling techniques Perform an enterprise analysis in preparation for determining requirements Analyze business processes to discern problems Foundation Concepts Overview of business analysis and process improvement Defining the business process Introducing the proactive business analyst Focusing on business process improvement for business analysts Launching a Successful Business Process Improvement Project Overview of the launch phase Understanding and creating organizational strategy Selecting the target process Aligning the business process improvement project's goals and objectives with organizational strategy Defining the Current Process Overview of current process phase Documenting the business process Business modeling options: work-flow models Business modeling options: Unified Modeling Language (UML) model adaptations for business processes Analyzing the Current Process Process analysis overview Evaluation: establishing the control group Opportunity techniques: multi-discipline problem-solving Opportunity techniques: matrices Building and Sustaining a Recommended Process Overview of the recommended process and beyond Impact analysis Recommended process Transition to the business case Return to proactive state

Agile and Scrum Fundamentals: In-House Training The overall goal of the course is to provide learners with the fundamentals of what Agile and Scrum are, and how to effectively apply Agile methods in your projects. What you will Learn At the end of this program, you will be able to: Describe Agile and Scrum foundation concepts Compare and contrast Agile roles to traditional roles Initiate an Agile project Develop Release Plans Build an Iteration Plan Execute an Iteration Implement Agile in your environment Getting Started Introductions Workshop orientation Expectations Foundation Concepts Project Lifecycles What is Agile? Why Agile? A range of Agile methods Focus on Scrum The People Side of Agile A range of Agile roles Focus on Scrum roles Unique characteristics of Agile Teams Building effective Agile Teams Initiating an Agile Project Conducting Sprint Zero Setting the vision Building the Product Backlog and User Stories Defining Acceptance Criteria Planning Releases Planning releases Estimating user stories Prioritizing user stories Selecting a Sprint length Estimating velocity Creating a release plan Planning an Iteration Conducting the Sprint Planning Meeting Building the Sprint Backlog Creating a Sprint Plan Running an Iteration Executing Sprint activities Using Burn-down and Burn-up Charts Negotiating changes during a Sprint Conducting the Sprint Review Meeting Implementing Agile Conditions of success for implementing Agile and Scrum Implementing Agile Final words

Writing and Managing Requirements Documents: In-House Training This course is part of IIL's Business Analysis Certificate Program (BACP), a program designed to help prepare individuals pass the IIBA™ Certification exam to become a Certified Business Analysis Professional (CBAP™). Learn more at www.iil.com/bacp. Once a business analyst has completed the information gathering and analysis to produce the solution to a business problem, the results must be documented for all stakeholders to see and understand. This course will enhance the skill set needed for writing and managing the complex readership that business analysts interact with on a day-to-day basis. What you will Learn Upon completion, participants will be able to: Write an understood requirements document that is approvable and acceptable Validate a requirements document Manage the changes to requirements documents through the SDLC Foundation Concepts The role of the business analyst An introduction to the BABOK® Guide The business analyst and the product/project life cycle The requirements documentation process Planning for Effective Requirements Documentation Overview of requirements planning Planning for validation Planning for verification: well-formed criteria Planning for verification: understood and usable criteria Writing Effective Requirements Documents Overview of writing requirements documents Using a standard structure / template Applying formatting techniques Meeting the challenge of writing non-functional requirements Baselining Requirements Documents Overview of the requirements baseline process Validation Verification Approval Managing Requirements Change through the Product Life Cycle Overview of requirements change management Establishing a formal change management process Tracing requirements through design and development (build, test, and implementation) Following through to post-implementation (transition and early production)

The Agile Project Manager Change isn't coming, it's already here. The project environment is becoming more volatile, uncertain, complex, and ambiguous. Project management and project managers must transform and evolve in order to keep up with these changes. Agile has been a disruptor in the field of project management, having over 20 years of successes and benefits to organizations that have adopted their frameworks. The Agile frameworks have proven themselves to be more adept in dealing with this uncertainty. But Agile isn't just about following a different way of working. What do you need to learn, do, and become in order to continue in the current and future environment? It is a powerful combination of knowledge, competencies, and mindset. In an increasingly complicated project environment, this course provides participants with the knowledge needed to not only survive but thrive. What you will Learn At the end of this program, you will be able to: Evaluate the changing project environment and the needed knowledge, skills, and behaviors Demonstrate innovative project manager competencies of leading change, servant leadership, and focus on value Utilize Lean and Agile principles to maximize value and improve project performance Construct a hybrid Agile model that is unique to your project Assess your role in Business Agility as an Agile Project Manager Getting Started Introductions Workshop orientation Expectations Foundations Recap: What is Agile? A changed project environment The future project manager Agile Project Management Competencies Focusing on value Championing change Servant leadership Coaching / mentorship Facilitation Lean and Agile Principles Optimizing flow Making things small Continuous planning Just-In-Time requirements Visualizing work Hybrid Agile Considerations Considering a Hybrid Approach Examining Strengths and Weaknesses of Each Approach Selecting Waterfall / Agile Roles, Practices, and Techniques Reviewing Three Hybrid Scenarios Constructing the Hybrid Project Implementing Agile Pitfalls and Concerns Agile in the Organization Business Agility

Estimating for Business Analysts: In-House Training A business analyst does not have authority to estimate the project and will not be held responsible for the project staying within the proposed budget; however, the business analyst does participate in various planning exercises with the project team. Many times the business analyst is on his or her own, required to provide estimates of how long it will take to perform their tasks. This course acquaints you with the basics of estimating from the point of view of the business analyst, emphasizing time estimates for the work. It also covers some of the product cost estimates that a business analyst may have to provide when the business is performing a cost/benefit analysis for the project. What you will Learn You'll learn how to: Translate business needs and requirements into estimates Estimate durations using a variety of techniques Negotiate differences in estimates Getting Started Introductions Course structure Course goals and objectives Foundation Concepts The importance of estimating to a business analyst The good and bad of estimating The project context The meaning of good estimating Focuses of estimating Characteristics of a good estimate Estimating the Time Requirements Applicable BABOK® Knowledge Areas Business Analysis Planning and Monitoring Elicitation and Collaboration Estimating the elicitation Information Gathering Plan Relative times for elicitation activities Planning and estimating the business analysis approach and activities Planning the business analysis activities Impact of process Estimating the Product Estimating the value of the product Business analyst's role Defining and determining value Function and use case points Agile estimating Planning Poker Other agile estimating techniques Negotiating estimates Negotiation techniques Negotiation approaches Summary What did we learn, and how can we implement this in our work environment?