PMI-ACP Certification Preparation Course

Explore the agile framework with three roles: product owner, scrum master, and team; ceremonies sprint planning, sprint review, and daily scrum; artifacts product backlog, sprint backlog, and burndown chart.

Learn how the scrum master shields the cross-functional team, supports selecting the sprint goal, and facilitates daily scrums and key ceremonies to deliver working software.

Learn how the agile manifesto prioritizes individuals and interactions over processes and tools, working software over documentation, customer collaboration over contract negotiation, and responding to change over following a plan.

Prioritize people and their collaboration as the foundation for agile success. Emphasize working software over documentation, customer collaboration over contracts, and adapting to change over a plan.

Learn the 12 principles of agile software development, emphasizing customer collaboration, early and continuous delivery of valuable software, welcoming changes, frequent working software, and self-organizing teams.

Explore agile principles from co-location and face-to-face communication to delivering working software, sustainable development, technical excellence, simplicity, self-organizing teams, and regular retrospectives.

Master stakeholder management in agile projects by identifying stakeholders, mapping support, and executing a robust action plan with intensive communication to secure commitments from both business and technical sides.

Apply agile stakeholder reporting by using a burn up chart for progress and noting that the customer specifies acceptance tests; share a roadmap for stakeholders seeking detail beyond the vision.

Evaluate agility concepts like balancing flexibility and stability, creating and responding to change in turbulent environments, and delivering customer value, while recognizing that avoiding planning conflicts with agile principles.

Identify the main scrum roles and events, confirm what constitutes a scrum team, master, and product owner, and analyze waterfall drawbacks vs scrum advantages in agile practice.

Apply the agile approach by using just enough design upfront to establish a solid foundation, mitigate risk, and start with the most relevant features.

Identify that agile delivers business value quickly with quality, not quick fixes; independent facilitation improves workshops, and teams collaborate to deliver early customer value.

Explore how agile teams meet regularly, use information radiators for reporting, and apply necessary documentation, while collaborating with customers and developers to prioritize features and deliver working software incrementally.

Explore agile values and team attributes, noting that working software overrides documentation, and that trust, courage to change, and responsiveness shape agile teams delivering business-valued increments.

This lecture explains agile motivation through celebrating small successes immediately, describes adaptive methods that empower teams to respond to change, and highlights product owner prioritization and stakeholder roles.

Create a concise agile project charter that defines vision, scope, constraints, assumptions, budget, stakeholders, and success criteria, guiding team alignment and a simple risk and communication plan.

Stakeholders write user stories using simple tools like index cards. They estimate size with story points and prioritize requirements, including defects, for online parking passes.

Explore practice questions for agile initiation, confirming that customer requirements are stored in the product backlog, the key Scrum artifact that guides release planning.

Explore how a product roadmap links releases to deliverables, and how a product owner prioritizes the backlog, documents with concise user story cards, and re-prioritizes as new requirements arise.

Learn agile release planning by organizing product backlogs into releases and release backlogs, then iterations, delivering time-boxed, shippable increments with sprint demos and continuous feedback.

Release planning defines the contents of a release by setting a goal, prioritizing stories by value and velocity, and deferring iteration assignments to iteration planning.

Hold a release planning meeting to secure buy-in on the release scope and date from the product owner, developers, testers, and the scrum master, discuss goals, velocity, and story estimates.

Split stories to fit release goals, adding a spike for technical unknowns and evaluating risk and complexity. The product owner selects from wish list to form release plan with consensus.

Explore story maps as a visual tool to group and relate user stories for release planning, integrating with the product backlog to plan releases and sprints.

Compare story maps with the product backlog to visualize a two-dimensional view of priorities and how user activities fit into a releasable product, identifying user roles and planning releases.

Story maps, popularized by Geoff Paton, group related user stories to show user goals, break work into functional tasks, and plan releases by iterations for early delivery.

Build a story map by defining user roles, activities, and user stories, prioritize from top to bottom, validate with stakeholders, and plan releases by aligning subtasks to release goals.

Discover how agile prioritization delivers maximum business value by focusing on the top 20% of features, cutting waste, and aligning the backlog with value, risk, and the product owner.

Apply agile prioritization techniques for release planning, including Moscow and the Kano CanAm model. Prioritize the requirements list from must-haves to satisfiers and incremental value to maximize customer impact.

Learn affinity estimating, an agile technique to quickly size a backlog of user stories in story points using a wall and cards, following a five-step process.

Teams size backlog items on a wall with s, m, l, xl, leaving space between buckets; product owner challenges estimates, items may be resized, then transfer to the tool.

Learn Wideband Delphi and planning poker, two consensus-based estimation methods for software projects, using group discussion, private card estimates, and iterative convergence to a single estimate.

Explore innovation games that help the product owner and team prioritize backlog by comparing cost and value, using Bang for the Buck and SWOT analysis.

Apply a SWOT-based release planning exercise to identify strengths, weaknesses, opportunities, and threats, cluster ideas, and use dot voting to align your team toward the desired end state.

Explore how to prioritize your product backlog through swot analysis and innovation games—speedboat, prune the product tree, pros and cons, and plus delta—aligning with market needs and customer value.

Explore gamestorming to turn ideas into feasible solutions, and apply empathy map, cover story, and impact and effort metrics to balance stakeholders and refine the backlog toward pmi-acp certification goals.

Explore release planning through practice Q&A on grouping related user stories for estimating and release planning, highlighting the concept of a theme.

Learn how to develop a capability based release plan to deliver a vision by speculating features, distinguishing speculation from envision or exploring.

Explore release planning through practice Q&A, calculate iterations from story points and velocity, and understand agile planning horizons—release, iteration, and day-to-day work.

Explore how the speculate phase delivers product stories and cuts risk. In release planning, assign stories to iterations by value and risk, with estimates at iteration planning and during iteration.

practice release planning in agile through q&a, clarifying backlog-driven scope, rolling-wave planning, product owner roles, risk management, and calculating relative feature contribution.

Standardize iterations to two weeks to simplify planning, measure velocity, and adjust scope quickly with predictable demo days and stakeholder coordination.

Review the prioritized backlog with the product owner, select stories for the current iteration, estimate tasks to deliver the increment, and confirm team commitment within a two-week sprint.

Illustrates prioritizing backlog items—features, defects, and requests—into iterations with two-week durations and resources, three stories per iteration, each with a code-test cycle, followed by iteration review and a product release.

Limit planning to four hours on day one; estimate work in hours or story points. Split stories to six tasks and ensure a demonstrable function; no changes during iteration.

Explore the daily stand up, or daily scrum, where a 15-minute status update helps teams identify impediments, coordinate work, and rapidly resolve issues in agile and scrum contexts.

Lead a daily stand-up to synchronize the team with a 15-minute, chairless meeting at 8:30 or 9:00, in front of the task board. Each member covers yesterday, today, and blockers.

Explore the five goals of the daily stand-up—start the day well, pursue improvement, focus on the right things, reinforce team synchronization, and communicate status—framed as gifts for your project.