Learn The Basics of Agile Project Management (DSDM)

Explore agile fundamentals: embrace flexibility, involve the customer, and defer details to the last responsible moments to ensure the solution meets the business need.

Explains agile concepts through lightweight approaches like scrum, lean, and extreme programming, and through more extensive programs, with a focus on DSDM and evolving customer needs.

Explore how to choose an agile approach by assessing project background, simple versus complex environments, backlog characteristics, cross-project dependencies, integration needs, and organizational structure.

Identify factors for selecting an agile approach for project management, including a complex environment, management support, and corporate culture, and compare scrum, lean, extreme programming, and DSDM.

Engage in an exercise to explore why you would use agile, and why you would choose agile DSDM for project management.

Review what agile is and how to select an appropriate agile approach. Preview the philosophy, principles, and project variables of an agile project.

Explore the eight agile principles—keeping the business need in focus, delivering on time, fostering collaboration and quality, and building incrementally from a solid foundation through iterative development and continuous communication.

Collaborate effectively in agile DSDM projects by involving the right business stakeholders, ensuring stand-up visibility and timely feedback, and empowering team members to decide within a one-team coach framework.

Iterative development turns high-level concepts into business value through short, time-boxed cycles and continuous collaboration, incorporating change and feedback from the solution development team in every sprint.

Discover how to communicate clearly and continuously in DSDM projects by using workshops, requirements modelling, time boxing, visible activity and outputs, and lean documentation with transparent stakeholder involvement.

Demonstrate control by aligning a clearly outlined plan to an agreed business objective, ensuring transparency, visible progress, and delivery focus through time-box plans and regular reviews.

Make the eight agile principles visible and empower every team member to raise flags when breached. Organize start-of-project workshops and sprint reviews to align on principle application and adapt behavior.

Explore the eight principles of agile DSM projects, the project philosophy, and why quality isn't a variable, through an exercise with follow-up discussion and recap.

Engage in active ongoing business engagement with timely demos to prevent project delays. Empower a stable, skilled solution development team of 8–10, embracing DSM with iterative development and open communication.

Explore the project approach questionnaire (PAQ) as a feasibility and foundations tool to assess success factors, identify risks, and capture stakeholder responses that shape the agile project approach.

Answer the essential questions to identify what is needed to prepare for a successful agile project, demonstrating readiness for agile project management.

We recap our progress in agile adoption, reviewing what agile is, how to select an appropriate approach, and the philosophies, principles, and project variables; next, the DSD process.

Learn the DSDM process from pre project to post project, emphasizing feasibility, foundation prioritization by Moscow, and iterative evolutionary development culminating in deployment.

Articulate the number of processes in agile project management and outline what each process entails, answering the questions on process and seeking feedback.

Recap the agile project management series, highlighting selecting an agile approach, philosophy and principles, time, quality, and scope variables, and preview DSM roles and responsibilities.

Introducing agile project management roles and responsibilities, the lecture outlines three broad areas—project roles, solution development roles, and supporting roles—with color-coded categories to identify business, solution, and management interests.

Serve as the project's technical authority, providing vision and coherence to meet the agreed standard, acting as a solution architect and advising on technical decisions as the senior technical person.

The business ambassador, a solution development team role, represents the business, drives day-to-day communication, and guides input to requirements to ensure the evolving solution aligns with the business case.

Discover the business analyst role in a DSDM project, integrated with the solution development team to translate business requirements into actionable details and foster clear business–team communication.

Explore the SDT team leader role within the solution development team in agile design projects, emphasizing leadership, peer election, and detailed planning of product delivery.

Explore the business advisory role in agile project management, where the advisor contributes specialist input to development and testing, represents business interests, and offers regulatory or legal guidance.

Identify and explain the technical advisor as a supporting role providing specialist input to the project, guiding deployment, operations, and post-live ownership.

The terms of reference functions as a pre-project, high-level definition of objectives and business drivers, outlining the scope and justifying feasibility investigation before the project begins.

The business case provides an evolving justification for the project, outlining expected business changes and potential benefits, and serves as a baseline for feasibility, foundation, and development with periodic reviews.

The prioritized requirement list (PRL) provides a high-level, prioritized description of project requirements to meet objectives, similar to a scrum product backlog.

Explain the delivery plan and management approach definition for agile projects, outlining high-level delivery dates, increments, and time boxes, plus organization, stakeholder engagement, planning, and progress demonstrations.

Explore the benefits assessment as a post-project description of realized benefits linked to the business case, and learn how color-coded categories (business, product, and management) govern project outputs.

Build a 14-item table listing each product name, its category (business oriented, technically oriented, or management or control oriented), and its governance status (get it or not).

Recap the agile approach within the DSDM framework, highlighting ideas, principles, project variables, success factors, processes, roles, and the DSM project lifecycle.

Integrate testing early in the project with a clear strategy and shared responsibilities. Foster collaborative, repeatable regression testing, apply Moscow rules, independent testing, and test-driven development.

Explore tracking and control concepts in agile project management, including time boxing, outcome-based measurement, transparency via a team board and daily stand-up, and management by exception.

Explore planning across the project lifecycle in DSDM, from pre-project feasibility to evolutionary development, using time boxes, resources, and integrated testing to refine delivery and realize benefits.

Discover how planning and quality guide the DSDM lifecycle, from high-level risk analysis in the pre-project phase to end-to-end testing and deployment, aligning requirements with quality measures.

Explore planning and control in DSDM, including two planning horizons, six testing concepts, tracking and control concepts, and lifecycle planning across pre-project, feasibility, foundation, and evolutionary development phases.

Explore MoSCoW prioritization, defining must have, should have, could have, and won’t have requirements across project, increment, and time box levels, to guarantee viable delivery within a time frame.

Examine Moscow prioritization with the MoSCoW M, S, C, W acronyms, and learn how DSM timeboxing phases, daily stand up, and project plan fit together.

Explore iterative development in the DSDM framework, with two to four week cycles, thought-action-conversation, configuration management, continuous verification, peer reviews, and positive, negative, and unusual-event tests.