Agile Project Management Certification Prep+Agile Scrum+Jira

Explore the learning objectives of the Agile Manifesto, focusing on its values, principles, and how to apply agile practices in project management, Scrum, and Jira.

Explore the agile manifesto and its core values: individuals and interactions over processes and tools, working software over documentation, customer collaboration over contract negotiation, and responding to change over plans.

Trace the birth of the Agile Manifesto from a three-day 2001 Snowbird meeting of 17 self-motivated software practitioners, who signed and laid foundations for a values-based agile alternative to waterfall.

Explore the four agile values: individuals over processes and tools; working software over documentation; customer collaboration over contracts; and responding to change over plan—and how they guide project priorities.

Embrace agile principle one: early and continuous delivery to satisfy the customer by delivering value quickly, with customer feedback at the end of every sprint guiding development.

Embrace changing requirements to maximize customer satisfaction, even late in development, by partnering with the client, embracing feedback, and weighing costs and benefits before changes.

Agile principle 4 requires daily collaboration between business people and developers, with the product owner representing the customer and the team aligned to deliver a testable product after each iteration.

Build projects around motivated individuals, provide the environment, tools, and support, and trust them to deliver; empower open communication and self-organization to drive agile progress.

Agile principle six assigns face to face conversation as the fastest, most effective way to convey information within a development team, using daily standups and video conferencing when needed.

Adopt a sustainable development pace with an eight-hour workday to prevent burnout and monotony across iterations from planning to feedback, preserving work-life balance in agile teams.

Maintain agility through continuous attention to technical excellence and good design, using small releases, refactoring, pairing, and continuous integration to reduce technical debt and speed time to market.

Maximize simplicity by eliminating unwanted, non-value adding work and delivering a simple architecture, design, and user stories that get products to customers quickly.

Self-organizing teams drive the best architectural design and requirements, relieving leaders and enabling backups, while the product owner defines what and the team decides how.

Reflect at regular intervals to become more effective, conduct the end-of-iteration retrospective, apply corrective actions to the next iteration, and drive continuous improvement in agile teams.

Explore the learning objectives of extreme programming (XP) within agile project management, aligning XP practices with Agile Scrum and Jira workflows.

Explore Extreme Programming (XP) as a lightweight agile method for small teams, emphasizing pair programming, code review, unit and integration testing, continuous integration, refactoring, simple design, and on-site customer collaboration.

Learn the learning objectives of Scrum within agile project management and explore how Jira supports Scrum practices.

Explore how Scrum replaces waterfall with iterative sprints, roles, artifacts, and ceremonies to deliver a potentially shippable product every 1–4 weeks.

Lead a sprint planning meeting by detailing the product backlog and confirming readiness to present, then secure a commitment to deliver the sprint on time.

Product owner presents sprint backlog items and acceptance criteria, while the team asks questions to determine what they can commit to and prioritize for maximum value.

Break stories into subtasks with estimates in the second half of the meeting to plan and commit to the sprint, guided by the product owner and Scrum Master.

Explore learning objectives for Kanban in agile project management, and connect them to Scrum and Jira workflows.

Discover Kanban's visual cards and pull-based workflow to limit work in progress and smooth delivery. See how three-bin and inventory detail cards prevent bottlenecks and oversupply.

Identify your workflow as a sequence of steps and visualize it with a Kanban board using columns for steps and cards moving left to right to done.

Establish work in progress limits to manage multi-tasking in Kanban. Decide how many calls, leads, follow-ups, and closes run concurrently to maximize efficiency, with limits that vary by domain.

Learn lean objectives within agile project management, aligning Scrum practices and Jira workflows to boost efficiency and value delivery.

Explore lean manufacturing principles that maximize customer value by mapping value streams, eliminating waste such as overproduction, excess transport, scrap, and waiting, and speeding flow to customers to reduce costs.

Embrace lean to help organizations adapt to inevitable change, cut excess inventory, and meet increasingly demanding customers by delivering lower costs and better results in a shrinking, connected market.

Explore lean as a philosophy rooted in kaizen, where change is good and lean is a mindset—not an event, guiding Toyota's tortoise approach.

Trace the history of lean and debunk the myth that lean originated with Toyota. Discover how the mindset to see and eliminate waste began at Ford.

Master lean fundamentals by applying five s, which stands for sort, straighten, shine, standardize, sustain, to identify abnormalities, map value streams, and implement pull with kanban for smooth cellular manufacturing.

Apply lean philosophies by embracing kaizen as a lean mindset that asks, how can we improve something today, going to the Gemba to observe work and learn from failure.

Lean software development emphasizes delivering maximum value to customers with speed and low cost through an empowered, effective team and continuous process improvement for high quality products.

Lean in action shows how software teams break requirements into unit features, identify customer value, and limit work in progress to prevent bottlenecks.

Define the learning objectives for DSDM in agile project management and align with agile Scrum and Jira.

Explore the dynamic systems development method (dsdm) as a standalone full lifecycle, agile project management and delivery framework with governance guidance, deliverables, and options for integration with other approaches.

Explore how DSDM, formed in 1994 by a non-profit consortium, centers on customer involvement to deliver rapid, robust projects on time and on a budget, shaping the agile manifesto in 2001.

Understand how the DSDM framework delivers business value by aligning projects to clear goals, delivering frequently, and guiding empowered collaboration from business need to live, evolving solutions.

DSDM offers a dynamic, adaptable agile project management framework that can wrap around Scrum, extreme programming, or other agile approaches and align with Prince2 governance.

Apply DSDM principles to govern the entire project life cycle, emphasize business needs, foster active user involvement, and deliver iterative, incremental solutions on time with quality.

Explore DSDM roles and responsibilities through a space alien diagram, detailing head roles and body roles, including business sponsor, project manager, team leader, and business ambassador for scalable agile projects.

Learn DSDM key practices and techniques, including facilitating workshops, modeling, Moscow prioritisation, iterative development prototypes, and time boxing with a three-cycle process of investigation, actual work, and consolidation.

Clarify learning objectives for other agile practices within agile project management, aligning them with Scrum and Jira.

Explore continuous delivery by building an automated pipeline from source control management through deployment to production, with continuous integration, systems integration testing, operational acceptance testing, security, and compliance checks.

Capture requirements as user stories from the user’s perspective using story cards and acceptance criteria. Prioritize and estimate the backlog by placing story cards on the wall to chunk work.

Explore acceptance test driven development (ATDD) in agile delivery, using automated living executable tests and collaboration among testers, developers, and stakeholders to drive rapid, quality software changes.

Learn how behavior driven development bridges business and tech teams through the three amigos, creating an executable specification that keeps customers in focus and improves quality in agile environments.

Explore how Jira supports agile scrum teams by setting up a first scrum project, organizing sprints, product backlog, user stories, and tasks with transparent reporting.

Set up Jira scrum project from scratch, build product backlog with epics and user stories, plan sprints, estimate with story points and time tracking, and monitor progress with burndown chart.