Agile BM 201 Mastering Agile Business Management

Explore the four agile manifesto values and their role in adaptive projects. Emphasize individuals and interactions, working software, customer collaboration, and responding to change over processes, documentation, contracts, and plans.

Explore the Agile Manifesto principles, focusing on early and continuous delivery of valuable software, welcoming changing requirements, and delivering working software frequently to enable customer feedback and continuous improvement.

Continuing the Agile Manifesto principles, this lecture highlights collaboration between business sponsors and development teams, empowered individuals with environment and support, and face-to-face communication as the preferred method.

Delve into the agile manifesto principles: working software as the primary measure of progress, sustainable pace, and continuous attention to technical excellence and good design.

Master agile principles emphasize simplicity, incremental development, and the minimum viable product, while self-organizing teams drive best architectures and ongoing retrospectives for continuous improvement.

Develop an adaptive mindset by applying systems thinking to link processes, people, and tools within the business system, exploring complex adaptive systems and agile mindset.

Explore complex adaptive systems and their role in agile management, highlighting emergence, self-organization, co-evolution, simple rules, feedback, and adapting within a dynamic business ecosystem.

Explore design thinking as a human-centered, disciplined approach to problem solving that blends desirability, feasibility, and viability across the product life cycle, with real-world examples and agile relevance.

Explore the five stages of design thinking—from empathize to test—and how empathy, defining a human-centered problem, ideate, prototype, and testing enable non-linear, iterative user-centered solutions.

Explore how design thinking complements agile by balancing human engineering with fast delivery, leveraging user feedback to maximize customer value in agile projects.

Explore design thinking in action across Apple, PepsiCo, GE Healthcare, and hospital trauma teams, showcasing human-centered empathy, iterative testing, and a holistic product and service design.

Explore design thinking as both an ideology and a user-centric process that solves ill-defined problems, drives competitive advantage, and complements agile through creativity and iterative, user-focused solutions.

Explore Kanban principles, boards, and pull-based flow to optimize work in process, forecast performance with cumulative flow diagrams, and compare Kanban with Scrum in agile work.

Use kanban boards to visualize work flow from next to analysis, development, and production, using sticky notes or online tools. Real-time updates and burndown charts enable reporting for distributed teams.

Optimize agile project flow by applying Don Reinertsen's seven principles, from economic value prioritization and small, uniform work increments to cadence-driven sprints and decentralized decision making.

Explore the theory of constraints and its five-step method—identify the bottleneck, exploit, subordinate, elevate, and repeat—to accelerate process flow and improve throughput.

Discover how cumulative flow diagrams visualize work in progress and cycle time, reveal bottlenecks, and compare to burndown and burn up charts to guide improvements for efficient, predictable delivery.

Explore lean software development, its principles, and value stream analysis to reduce waste, improve efficiency, and connect lean origins in manufacturing to agile methods like Scrum.

Explore the seven lean software development principles, including eliminate waste, amplify learning, decide as late as possible, and deliver as fast as possible, and compare lean with agile.

Learn value stream analysis in lean software development, identify value and waste, and map current and future states to drive improvement with value stream mapping and the Five Whys.

Explore value driven delivery in agile methodologies, emphasizing delivering the right product that maximizes business value, and contrast with plan driven approaches through customer prioritization and a business case.

Discover four key principles of value driven delivery: define goals by business outcomes, acknowledge uncertainty, make trade-offs with objective evaluation, and deliver quickly to preserve value.

Master models and best practices for customer value prioritization in agile, from strategic themes and epics to tactical backlogs, balancing business value, dependencies, and available resources.

Explore how Pareto analysis identifies the 20% of features that drive 80% of value and apply Moscow prioritization to must, should, could, and won’t have requirements.

Explore customer value prioritization with the Kano model, detailing four feature categories—one-dimensional, must-haves, indifferent, attractive—and two questions to assess value, plus the use of JAD sessions to resolve inconsistencies.

Explore the relative weighting method for customer-value prioritization, similar to Kano, calculating relative weight and penalty, total value, value percentage, and feature priority by assessing cost and risk.

Compare traditional plan-driven business case development with agile approaches that acknowledge uncertainty, test hypotheses with limited prototypes, and use customer feedback and iterative, incremental learning to refine ideas.

Explore rolling wave planning and adaptive planning in agile projects, and apply incremental planning across release and iteration levels while embracing progressive elaboration and uncertainty management.

Learn to craft a concise product vision that defines business value, guides functional decomposition, and aligns agile teams around a shared true north for prioritizing hundreds of user stories.

Learn to build a goal oriented product roadmap in agile planning. Keep it dynamic, aligned with business goals, and secure stakeholder buy-in with clear metrics.

Explore agile planning through exploratory 360 assessment, identifying knowns and unknowns in chartering, with business value sampling, requirements sampling, domain model, technology plans, team makeup, and risk assessment.

Apply functional decomposition in agile planning to break complex processes into epics and stories, align with business goals, and improve backlog traceability and scope management.

Discover agile planning practices and tools, focusing on the minimal, informative project charter in agile projects, its components like scope, objectives, stakeholders, risks, and how it adds value.

Master progressive elaboration and rolling wave planning in agile projects through prototyping and feedback. Coordinate project, release, sprint, and daily standup planning as interrelated levels that adapt to new information.

Explore agile requirements best practices, including upfront planning balance, stakeholder involvement, product owner roles, prioritizing requirements, and organizing work with user stories, epics, themes, and story mapping.

The business analyst acts as a facilitator between developers, product owners, and users, translating requirements into well-organized epics and clear user stories that drive value in agile projects.

Define and model user personas to personalize agile requirements, centering value on specific users and guiding development with real or fictitious profiles. Visualize needs and benefits for targeted users.

Learn how user stories define agile requirements as brief placeholders for conversation, with the three elements as a role, I want something, so that, and Invest criteria.

Organize hundreds of user stories with epics and themes; epics are large, hierarchical containers needing breakdown, while themes group related stories without strict hierarchy to support releases and business objectives.

Define and maintain the product backlog as a dynamic, ordered list of user stories and epics, continuously groomed and prioritized by the product owner and team.

Map user tasks into a two-dimensional story map to visualize the backlog, prioritize releases, and drive iterative, walking-skeleton development with post-it brainstorming.

Explore agile risk management by comparing agile and traditional approaches, define risk, and apply iterative risk identification, assessment, planning, and monitoring to maximize project value.

apply agile risk management principles by integrating risk into the project, identifying risks early, communicating with customers, evaluating threats and opportunities, prioritizing, and planning responses with avoidance, mitigation, or acceptance.

Explore how agile risk management handles uncertainty by exposing risks, reducing unknown unknowns, known unknowns, and known knowns, and balancing action with project needs, contrasting with plan-driven approaches.