Mastering Agile Scrum Project Management

Define agile project management and explore how its adaptable, collaborative approach differs from traditional methods, while tracing its evolution in the digitized, fast-changing information world.

Compare traditional and agile project management through a hypothetical cell phone unlock feature, showing there is no one-size-fits-all method and that rapid market changes favor adaptable, iterative approaches.

Explore how agile methods prioritize stakeholder collaboration, flexible roadmaps, and rapid learning to adapt projects, reduce waste, and deliver earlier value through backlog-driven, iterative work.

Test your understanding of agile versus waterfall project management with a quick knowledge check, confirming that waterfall is a traditional project management method.

Discover the key disadvantages of agile project management, including dependency on active stakeholder involvement and fit for knowledge work over physical projects.

Identify a key disadvantage of agile project management: it is not applicable to all types of projects. Recognize that agile works best for knowledge work rather than physical manufacturing projects.

Treat agile project management as a flexible discipline, not a manual, and view it as a toolbox for navigating varied, choose-your-own-adventure style projects.

Explore the agile manifesto, its four core values, and the first six principles shaping agile project management, with PMI-ACP exam relevance and history for context.

Trace origins of the agile manifesto, drafted in 2001 at Snowbird with 17 attendees, and learn its four values: individuals over processes, working software, customer collaboration, and adapting to change.

Discover how the agile manifesto's concise values guide projects more than rigid steps. Apply the four agile values across methodologies, including non-technical contexts, to foster safe collaboration and software knowledge.

Explore four agile values from the manifesto — individuals and interactions over tools, working software over documentation, customer collaboration over contract negotiation, and responding to change over following a plan.

Engage with the agile manifesto by recognizing that responding to change supersedes following a plan, and apply this principle to agile scrum project management.

Prioritize customer satisfaction through early and continuous delivery of valuable software, engaging both internal and external customers, delivering early to gain feedback, and ensuring the work provides real value.

Embrace changing requirements, even late in development, to harness the customer's competitive advantage within agile processes. Agile change management is disciplined and streamlined through collaboration with product owners and customers.

Deliver working software or models frequently, even for non-software projects, to gather rich feedback and clarify visions, using short timescales to enable quicker decisions and wider stakeholder dialogue.

Collaborate daily with business stakeholders to gather feedback, using face-to-face conversations and a fixed daily cadence to drive agile project success.

Agile principle number five empowers teams by building projects around motivated individuals, providing environment and support they need, and trusting them to get the job done through collaboration and teamwork.

Face-to-face conversation remains the most efficient method for conveying information within a development team, even as dispersed global teams rely on technology.

Explore agile principle two by identifying that changes should occur any time during the project, and learn how welcoming late requirements harnesses the customer’s competitive advantage.

Explore the purpose and history of the agile manifesto and the four core values. Review the first six principles to guide value delivery and adaptability in agile projects.

Explore the agile manifesto as a guiding, value-based ideology for project management, covering its purpose, the four core values, the twelve principles, and the declaration of interdependence.

Review the first six Agile Manifesto principles, focusing on people and interactions, early and continuous delivery of valuable software, welcoming changes, and frequent face-to-face collaboration.

Take a knowledge check on the Agile Manifesto, recognizing that it does not standardize to a single method or enforce rigid rules.

Explore the final six Agile Manifesto principles, including working software as progress, sustainable development, continuous attention to technical excellence, simplicity, self-organizing teams, and regular reflection to improve.

Apply agile principle seven across projects by making working deliverables the primary measure of progress, driving feedback, testing ideas with measurable results, and reducing overemphasis on documentation.

Embrace sustainable development by maintaining a constant pace that lasts indefinitely for sponsors, developers, and users. avoid overambition, burnout, and fragile short-term gains, focusing on long-term project health.

Prioritize continuous attention to technical excellence and good design to enhance agility, and emphasize refactoring as essential to maintain stable, maintainable software.

Embrace simplicity by maximizing the amount of work not done, keep software simple and intuitive, and heed 'everything should be made as simple as possible, but no simpler'.

Unleash the potential of self-organizing teams and knowledge workers to produce the best architectures, requirements, and designs through servant leadership and a flat, collaborative culture.

Reflect regularly to become more effective, tune team behavior accordingly, and learn from failures and successes to improve agile scrum project management and share lessons.

Engage in a knowledge check on the last six Agile Manifesto principles, identifying that working software is the primary measure of progress, per the seventh principle.

Discover how the declaration of interdependence guides agile project leadership with a collective approach, emphasizing continuous value flow, frequent customer collaboration, adaptability, and shared accountability to deliver results.

Complete this knowledge check to learn that, per DOI, we increase return on investment by making the continuous flow of value our focus.

Review the agile manifesto and its twelve principles, condensing each into a word or two. Emphasize continuous value, welcome change, delivering frequently, working software, and self-organizing teams.

Conclude the discussion of the Agile Manifesto and agile principles, then transition into methodologies and applications for upcoming, more technical sessions as you pursue becoming an agile practitioner.

Explore agile project management with Scrum and XP, covering core concepts, terminology, roles, events, artifacts, and the definition of done, plus practical insights into certifications.

Embrace uncertainty with timeboxed sprints to manage chaos through stakeholder feedback. Discover customer needs by delivering small, workable increments and reorienting toward a shippable product.

Identify the three Scrum roles—product owner, Scrum development team, and Scrum Master—and their responsibilities, from backlog prioritization and ROI to safeguarding the product vision through osmotic learning.

Explore Scrum events, including sprint planning, daily scrums, sprint reviews, sprint retrospectives, and backlog refinement, to drive a potentially shippable product with self-organizing teams.

Learn about Scrum artifacts, including the product backlog, sprint backlog, and burndown charts, and how they remain a living, visible guide to priorities and progress.

Explore the agile theory behind scrum and its role in agile project management. Build team buy-in and practice to avoid legacy policies that hinder scrum.

Examine Scrum's three roles, Product Owner, Scrum development team, and Scrum Master, and learn their distinct responsibilities in this knowledge check before moving to extreme programming.

Explore extreme programming (XP) as an agile software method, focusing on user stories and the invest criteria—independent, negotiable, valuable, estimable, small, testable—and timeboxing.

Explore extreme programming’s core values—simplicity, communication, feedback, respect, and courage—and how they drive simple designs, open collaboration, early feedback, and shared code.

Align the whole team in XP agile project management by locating near each other and including the customer as a constant voice, enabling flexible roles and continuous collaboration.

Unite business and development in the XP planning game to shape release and iteration plans. Explore, commit, and steer with the customer through user stories and two-week iterations.

Embrace small releases to enable frequent deployments and feedback, ensuring transparency and early error correction. Showcase progress with contribution lists and annual charts, iterating through wireframes to improve quality assurance.

Explore xp core practice customer tests, involving customers in testing to create a fast feedback loop between business and development and deliver working software through small releases.

Embrace collective code ownership to keep the whole team involved, boost transparency and knowledge sharing, and empower any member to step in and contribute.

Implement code standards to guard against collective code ownership risks, creating a unified approach so the project’s code reads as if written by one, across teams and languages.

Practice continuous integration and small releases to keep a constant pulse on code quality through daily integration testing, with early detection and quick fixes of breaks.

Translate technical work into non-technical terms to improve stakeholder understanding; use metaphors and analogies as a core XP practice to communicate project efforts.

Learn how extreme programming promotes a sustainable pace to prevent burnout, maintain morale, and sustain productivity by aligning work with a forty-hour week and steady velocity.

Pair programming amplifies the collective brain trust by having two developers work side-by-side, enabling real-time feedback, quicker error detection, and shared knowledge.

Practice test-driven development by setting up tests at the start to verify features, failing early to guide coding and ensure quality from the outset.

Master Extreme Programming's refactoring practice to produce clean, efficient code that remains true to its intent and team standards.

Master the XP core practice of simple design, emphasizing simplicity to mitigate risk and set the project up for success. Teams focus on the simplest design to achieve the goal.

Mastering agile scrum project management presents an extreme programming knowledge check, highlighting user stories as a major XP piece and how lightweight requirements express user needs through a persona.

Recap Scrum and XP concepts, key terms, roles, and practices. Highlight sprints, the product backlog and sprint backlog, the definition of done, XP values, and the INVEST mnemonic.

Conclude with a reminder that Scrum and XP were briefly explained and are not replacements for full courses. Encourage learners to explore more and apply agile practices to real-life projects.

Explore lesser-known agile method types beyond scrum and XP, including DSDM, Kanban, Crystal, Lean, and Adaptive Software Development. Build a broader toolkit for timeboxed projects.

Explore the dynamic systems development method (dsdm), an agile framework built on eight principles—focus on business need, timely delivery, collaboration, and quality—to deliver iteratively with timeboxing and continuous communication.

Kanban, born in manufacturing from Toyota's just-in-time system, translates lean principles into agile practice by visualizing workflow on a Kanban board, limiting WIPs, and pulling work toward done.

Explore lean software development and its seven core concepts, including eliminating waste (muda) with value stream mapping, amplifying learning through early testing, and delivering fast to speed up feedback loops.

Explore the Crystal family of ultralight agile methods for small teams, tailored by criticality and team size. Apply seven practices, including frequent delivery and osmotic communication.

Explore feature-driven development (fdd), an agile, client-centric, architecture-centric method that delivers client-valued features through five activities and short, iterative builds.

Discover adaptive software development, an evolution of rapid application development and waterfall, guided by speculating, collaborating, and learning cycles for frequent builds and timely feedback.

Compare agile project management methods beyond XP and Scrum, including Dynamic Systems Development Method, Crystal Family of Methods, Kanban, Lean Software Development, Feature-Driven Development, and Adaptive Software Development.

Explore the Crystal agile method in a knowledge check, mapping project criticality and team size to color levels from Crystal Clear to Crystal Magenta.

Explore the mechanics and practices of agile methods, uncover concepts that transcend all methods, and advance toward the PMI Agile Certified Practitioner certification while maintaining momentum.

Learn value-driven development for agile project management by identifying customer value, assessing roi and financial metrics, prioritizing work with stakeholders, and delivering high-value projects through roadmaps, prototypes, and risk-aware contracts.

Drive agile value by clarifying what matters, delivering high-value items early, and using stakeholder feedback to guide resource allocation and reduce waste.

Master agile scrum project management by mastering incremental delivery, delivering value in small, iterative increments, gathering rapid feedback, and refining product scope through customer feedback.

Explore value-driven development for project justification and selection, weighing impact and effort across four organizational considerations in agile project priorities.

Formulate a clear business case with financial or perceived justification, supported by market research and feasibility studies, to justify value-driven development, consider opportunity costs, and reduce risks.

Evaluate opportunity costs by weighing the benefits lost when choosing one project over another. The lecture explains how selecting the security issues project costs the employee app and other opportunities.

understand the internal rate of return (IRR) as the rate tied to present value and expected cash flows, signaling a project's growth potential and guiding selection with NPV and ROI.

Explore how value-driven development measures return on investment (ROI) and value on investment (VOI) in agile projects, including financial gains, efficiency savings, and increased employee confidence and standardization.

Assess net present value, present value, and estimated value as measures of a project's economic value. Analyze cash inflows and outflows to determine whether npv is positive.

Identify and manage risks, both threats and opportunities, as uncertainties, to drive value in agile projects by integrating risk management throughout the project lifecycle.

Explore how agile project management uses the Kano model and MoSCoW prioritization to evaluate customer value and prioritize features through stakeholder input.

Leverage prioritization lists and the overall product plan to decide what to include in current projects, while roadmaps outline high-level outcomes and milestones over time.

Agile contracting frames contracts as agreements with rules of engagement that define roles, responsibilities, accountability, and high level expectations, enabling flexible adaptation when scope is not definitely defined.

Use the inverted triangle model within the DSDM framework to shift contract terms from scope to time and resources, aligning deliverables with resource and time controls for agile delivery.

Discover how agile contracts incorporate traditional procurement items, with fixed price contracts and work packages, including renegotiation windows, and why fixed prices pose risk in agile projects.

Explore graduated fixed price and incentive clauses that reward on-time, high-quality delivery, contrast with time and material contracts, and learn pricing controls like floors and ceilings in agile projects.

Explore Jeff Sutherland's 'money for nothing and the change for free' method, where a customer can draw a line to terminate work or request free changes by shifting scope.

Explore the Kano model, analyzing customer needs and expectations of features, functions, and other product aspects. Learn its origin from Dr. Noriaki Kano in the eighties during this knowledge check.

Capture value for customers by formalizing the project through chartering, securing sponsorship, and outlining budget, resources, and a start-to-end time frame.

Capture data that demonstrates earned value to prove delivery against the project's intended value, and communicate progress with burndown charts, information radiators, prototypes, and early customer feedback.

Identify the primary purpose of project chartering as formal authorization to use company resources, ensuring the project exists and can be managed.

Define value and assess it against product roadmaps to drive value-driven delivery, prioritize features with MoSCoW, Kano, and fake money, and select projects via contracting options and net present value.

Conclude by recognizing why projects are selected and how delivering value aligns with goals and certification. Keep sight of purpose to guide the agile team toward the right direction.

Prioritization drives agile project planning, aligning stakeholders as we develop the product vision, business case, roadmaps, and backlogs while integrating risk management at a holistic level.

Prioritize value by linking the product vision to a roadmap and release plan, then plan iterations and daily standups to showcase progress through sprint reviews and retrospectives.

Define and communicate a clear product vision in simple terms to align stakeholders, justify the initiative with an agile business case, and guide the project from inception to completion.

Map the product vision into a story map to prioritize and sequence user stories, reveal interdependencies, and guide the walking skeleton toward a coordinated roadmap.

Discover how a product roadmap visualizes deliverables, timelines, and stakeholder alignment in agile planning. Prioritize features, tell a cohesive product story, and enable incremental delivery with feedback.

Learn how the product roadmap drives a prioritized backlog, with a story map guiding scope and prioritization, and a high-level plan shaping the product backlog for agile planning.

Learn how prioritization drives value in agile projects, delivering the most desirable features first through incremental delivery, and applying the 80-20 rule to maximize impact.

Explore methods to set product priorities in agile projects with team and stakeholder input. Apply gamified prioritization and devil's advocate methods, using affinity diagrams to avoid groupthink and encourage reprioritization.

Identify that the product owner spearheads and owns the product vision, while other stakeholders contribute. Reinforce agile roles and collaboration through this knowledge check.

Identify and manage uncertainty in agile projects by applying structured risk processes, acknowledging that agile risks resemble traditional project risks and require disciplined risk management.

Identify risks by recognizing uncertainties and the probability or likelihood of events along with their impact, since risk is the combination of likelihood and impact in agile and traditional projects.

Define risk severity as probability times impact, and use qualitative and quantitative risk assessments plus the risk burndown and EMV to guide mitigation and budgeting decisions.

Identify and implement proactive risk responses to reduce probability or impact, mitigate or avoid risks, and adjust the product backlog with gained insights to move the project forward.

Use a risk burndown chart to show progress in reducing the probability and impact of identified risks in agile projects. Communicate actively to demonstrate risk handling and minimize project effects.

Perform a knowledge check on how the product roadmap orders and bounds the product backlog, and why aligning backlog items to the roadmap clarifies priorities.

Define the product vision, create a story map and roadmap, and build the product backlog to guide agile delivery while proactively managing risks with a risk burn-down graph.

Explore how iteration planning drives agile projects by balancing upfront planning with adaptive, stakeholder-informed decisions, using sprints, backlog prioritization, and reviews to guide release plans.

Explore how agile project plans span strategic to daily levels, with adaptive, value-driven iteration planning, rolling wave elaboration, and sprint backlogs guiding releases and increments.

Publish planning results to all stakeholders to foster transparency, participation, and accountability, ensuring plans are current and invite input to inform decisions and expectations.

Master timeboxing to sharpen focus and manage work in agile Scrum by defining iterations as fixed timeboxes, prioritizing, planning, and committing only what fits the sprint.

Refine the backlog and plan releases through progressive elaboration, prioritizing value, decomposing work into minimal marketable features and slices, guided by the product owner and story maps.

Iterative planning applies progressive elaboration to agile iterations, refining estimates, work, and definitions as information evolves. Rolling wave planning guides detailing acceptance criteria, risk assessments, and testing over time.

Deliver workable, shippable increments early and often to gather real user feedback, capture usage data, and align minimal marketable features with stakeholder needs.

Ensure agile planning remains transparent by sharing all planning activities with all stakeholders, inviting input and fostering participation in iteration planning.

Use agile planning games to refine the backlog, prioritize features, and plan iterations with Prune the Product Tree, Sailboat, If I Had A $100, and Make and Move a Mountain.

Learn how iterations and sprints are interchangeable timeboxed periods in agile projects that limit distractions, build discipline, and boost teamwork and progress over two to three weeks.

Plan the upcoming iteration by prioritizing the backlog, detailing tasks and tests, and achieving a realistic, timeboxed, negotiated commitment among the product owner, development team, and agile project manager.

Allocate spikes to investigate architecture or technical questions; plan for them, as they consume sprint capacity and may affect estimates and future iterations, and should not exceed one sprint.

Use velocity to estimate a team's capacity from historical averages for guiding iteration planning. Recalculate velocity trends as iterations complete, considering work merits and changing factors.

Synchronize sprint work with a 15-minute daily stand-up to plan the next cycle, keeping it punctual, focused on the three questions, and free of side conversations.

Plan iterations by focusing on user stories, features, and tasks, including testing, validation, and documentation, rather than backlog items. Keep administrative activities minimal and do not affect iteration capacity.

Discover how progressive elaboration evolves details and plans over time in agile projects, with confirmation that it happens throughout the project lifecycle.

Master agile planning by examining planning iterations, sprints, timeboxing, and the philosophy of agile versus traditional methods, using velocity, minimal marketable features, and progressive elaboration to deliver potentially shippable increments.

Conclude your study of planning in agile projects and explore complementary courses on agile estimation and managing agile projects to wrap up iterations and improve planning and execution.

Explore how agile estimation uses user stories to gauge sprint and product backlogs, and map overall project duration with story maps, project plans, and sticky notes.

Compare agile and traditional estimation, embracing imprecision and change, and apply techniques like analogous, parametric, and three-point (PERT) estimates to set sprint and project timelines.

Apply progressive elaboration to agile estimation by making initial estimates with limited information and refining them as new data and stakeholder feedback emerge.

Leverage velocity to forecast sprint capacity using historical data and story points, ensuring apples-to-apples estimation from the backlog. Update projections for remaining work and budget as new data emerges.

Leverage throughput, the rate items pass through the system, to estimate sprint productivity and forecast future capacity by tracking work in progress to done on a kanban board.

Explore the three point estimation, also known as the Purt method, to account for optimistic, pessimistic, and most likely outcomes in agile scrum project management.

Define lead time as the duration from backlog entry to delivery, and estimate it to set expectations for work items. Compare with cycle time to plan delivery.

Learn how agile cycle time measures the interval between successive deliverable completions, such as user stories, and use it to estimate work in progress and future sprint throughput.

Distinguish ideal time from likely time when estimating agile work and adjust for interruptions and dependencies. Apply consistent, realistic estimates using story points and relative sizing.

Discover how agile teams use story points, relative sizing, and t-shirt sizes (with Fibonacci as an option) to estimate work quickly, plan releases, and manage risks.

Master agile estimation with collaborative games like Planning Poker, using the Fibonacci sequence to drive discussion, reveal risks, and build consensus across the team.

Explore agile estimation games, including affinity diagrams and Get My Drift, to boost participation and collaboration using wall layouts, sticky notes, and the Fibonacci sequence.

Learn how agile estimation evolves through uncertainty, learning, and short-term estimates, using velocity, cycle time, and story points, plus estimation games like Planning Poker and Wideband Delphi.

Explore how t-shirt sizing serves as a simple, relative sizing technique for agile estimation, reinforcing key concepts in measurements and estimations.

Concludes the course on estimation and measurements in agile projects within the broader agile project management and practitioner best practices series.