Agile Scrum Mastery & Kanban: The Complete Practical Guide

Define a project as a temporary effort with a start and finish that delivers something unique, such as a product, service, or outcome across contexts.

Differentiate projects from operations, noting projects are temporary and unique while operations are permanent and repetitive, with examples from a restaurant and a car manufacturer illustrating alignment with business objectives.

Explore how objectives drive outputs and outcomes through operational projects, turning opportunities into deliverables, with practical Scrum-based simulations to master its foundations.

Distinguish projects from operations and learn scrum as a practical path from start to goal. Master project management skills to deliver customer value with efficiency and adaptability.

Learn how projects organize the effort to manage, sustain, and retire products across the five lifecycle stages: introduction, growth, maturity, decline, and retirement, illustrated by the Orkut example.

Examine traditional project management as a plan-driven, upfront planning approach using Gantt charts and fixed bid contracts, with stages from initiation to monitoring and control and change resistance.

Explore how the iron triangle links scope, resources, and time in traditional project management, where the scope is fixed and estimates are used to negotiate contracts.

Explore the golden paradox of knowledge versus ease of change in project management, illustrated by early cheap changes versus costly late-stage adjustments and restrictive contracts.

Identify when traditional management fits projects with low scope uncertainty, informed by IKIWISI and YAGNI, with examples from architecture, software, bridges, and buildings.

Explore why projects fail due to unclear client requirements, miscommunication between business and tech, and evolving moving targets, along with essential versus accidental reasons and the role of stakeholder involvement.

Trace how 90s lightweight methodologies, including Scrum, emerged to fit complex software projects, and how the Agile Manifesto defines the values and principles behind Scrum.

Discover the agile mindset as the foundations of agile practice, emphasizing uncovering better ways, learning and adapting, collaboration with customers, short delivery cycles, and delivering value while embracing changes.

Explore the agile values that prioritize individuals and interactions, tangible deliverables, and customer collaboration to boost responsiveness to change and solve complex problems by enabling cohesive teams.

Compare traditional and agile approaches, illustrate how quick releases and customer feedback reshape the product vision, and emphasize lean waste reduction to reach the correct vision.

Explore the trade-offs of agile versus traditional paradigms, focusing on rework, continuous feedback, and the agile mindset that embraces change while maintaining ongoing planning and client involvement.

Organize the agile manifesto's 12 principles into four categories: project, product, people, and process—to simplify absorption and guide agile practice.

Master agile project principles by delivering valuable, working products early to gather informed customer feedback. Embrace short delivery cycles, welcome changes, and measure progress by the working product.

Discover how product principles emphasize simplicity, lean thinking, YAGNI, and deliver only what is necessary with autonomy and technical excellence.

Explore how agile emphasizes people, prioritizes face-to-face communication, selects channels to reduce noise, keeps business people involved daily, and values servant leadership and self-managed teams.

Regularly reflect to become more effective, then tune and adjust team behavior. Embrace continuous learning to optimize what and how we deliver, including people, processes, and tools.

Compare traditional and agile project management to help you understand their contrasts and decide which paradigm to apply.

Explore the cone of uncertainty and how uncertainty shrinks over time. Compare traditional planning with agile delivery to reduce estimate variability in volatile software environments.

Agile replaces the iron triangle of fixed scope, time, and resources with a people-driven deadline and evolving vision, using inspect and adapt to define a living emergent scope.

Recognize that there is no one-size-fits-all approach; traditional and agile work in contexts, so learn both and use them as tools, avoid fanboy mindsets, and let them complement each other.

Explore how Scrum’s core components relate to drive change, from the Product Backlog and Product Owner to Sprint Planning, Daily Scrums, Definition of Done, and the Increment.

Dissect Scrum to reveal its value-driven structure, showing how the product backlog guides value delivery. The product owner leads backlog quality and alignment with stakeholders to enable successful sprints.

Learn how sprints transform ideas into value in Scrum, with Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, while Product Backlog refinement continuously feeds successive sprint cycles.

Position the sprint backlog as the output of sprint planning and input for sprint execution, capturing the sprint goal, selected product backlog items, and scope.

Explore how the increment represents a vertical, usable product delivered each sprint, bridging architecture, layers from database to frontend, and enabling stakeholder feedback through sprint review.

Demonstrates how sprint retrospective drives future behavior of the product owner and developers, under an empowering scrum master, and why a solid definition of done is vital.

Explore the Scrum theory, its empiricism and lean thinking, and how its rules shape accountabilities, events, and artifacts.

Embrace empiricism by inspecting, adapting, and maintaining transparency through Scrum's events and artifacts, with short sprints to learn and improve, boosting predictability and risk management.

Learn how the five Scrum values—commitment, courage, focus, openness, and respect—bring transparency, inspection, and adaptation to life, empower the scrum team, and build trust with stakeholders.

clarify the scrum team roles, including product owner, scrum master, and developers, and how they collaborate to align the product backlog and product goal, delivering valuable increments each sprint.

The product owner maximizes value by managing the product backlog and communicating the product goal. They translate business ideas into prioritized backlog items for the scrum team.

Explore how a weak proxy product owner caused long feedback loops and rework, showing the need for a true product owner with authority and business knowledge.

Developers are cross-functional, self-managed teams that own all work to deliver usable increments each sprint, with no sub-teams, accountability, and autonomy to negotiate with the product owner for business alignment.

The Scrum Master serves the organization and the team, removes impediments, guides product backlog management, and coaches the team to self-organize and deliver valuable increments.

Explore the Scrum lifecycle in practice through a case study, from initiation and backlog creation to planning, execution, inspection, adaptation, and closure, with hands-on learning.

Explore how Scrum works by detailing events and artifacts through a real production web app case study. Use Proj4me to execute Scrum and apply the approach to your own projects.

Explore Konyu, a proxy service to bid on Yahoo Auctions Japan, featuring content management, language and currency settings, wallet funding, watch lists, and shipment options.

Learn how to create a project in Proj4me, a Scrum-friendly project management tool, and navigate the dashboard that shows project names and progress.

Kick off the project with initiation work by defining the initial product backlog before sprints, a living artifact that starts with known requirements and adapts through the project.

Define and align a motivating product vision using a vision board, mapping target groups, needs, and business goals, with a flexible strategy that can pivot toward a feasible MMP.

Save your defined product vision to proj4me by uploading an attachment from the project homepage, centralizing all project information in one place.

Clarify how Scrum artifacts—the product backlog, sprint backlog, and increment—drive transparency, alignment, and inspection through commitments like product goal, sprint goal, and definition of done.

Define the product goal as a measurable future state guiding the Scrum Team toward the product vision and strategy via the backlog, with the Product Owner leading the product goals.

Define a concrete product goal from the product vision with a six-month target, metrics, and features like sign up, product search, bidding, and international shipment to guide the Scrum Team.

Refine the product backlog with just-in-time details, converting large epics into testable user stories for the upcoming sprint. Visualize backlog health from epic to ready items and define ready criteria.

Explore the user story as a three-part artifact—card, conversation, and confirmation—written from the customer’s perspective, with actor, action, motivation, and clear acceptance criteria.

Learn how to order the product backlog to maximize ROI by weighing size, risk, value, and dependencies. See ROI calculations and examples.

Learn how agile teams estimate with story points and planning poker, not hours or days. A curve shows that small effort boosts accuracy; excess harms it.

Learn how agile uses relative sizing with story points on a semi-Fibonacci scale to estimate backlog items, using comparisons to a baseline and planning poker for team alignment.

Learn to estimate with planning poker, a collaborative, consensus-based technique using story points; teams discuss backlog items, reveal estimates together, and adjust through rounds to reflect team context.

Apply the Kano model to classify product backlog items into mandatory, linear, or exciter, then use survey data to prioritize and order the backlog for timely delivery.

Master how to manage the product backlog by keeping it deep, dive, and invest, with detailed, estimated, emergent, negotiable, independent, small, testable, and value-driven items.

Form the scrum team before sprints, assembling five to nine developers plus the PEO and the scrum master, while balancing hard skills, soft skills, and costs.

Develop a release plan to align the Scrum team and organization, defining what can be delivered by a date using feature-based or date-driven approaches, including epics, backlog, and localization.

Explore data driven release planning as an alternative to feature based release planning, and predict the team's capability across two week sprints and releases.

Calculate team velocity from sprint points to forecast release timing and capacity. Use historical data or observed velocity, account for the cone of uncertainty, then convert hours to points.

Plan releases with clear goals, noting releases aren’t mandatory at sprint ends and can occur during a sprint with a potentially releasable increment, enabled by continuous delivery.

Define the sprint length before planning, considering team size, maturity, automation, and stakeholder availability; the team or scrum master decides, keep it fixed for pace, and avoid changes after planning.

Define the definition of done before estimates to set clear criteria and ensure alignment, transparency, and quality across product backlog items, sprints, and releases.

Explore how teams sketch a preliminary systems architecture before a sprint. Understand why the term sprint zero is controversial, as it delivers architecture sketches without business value or an increment.

Boost collaboration by organizing an open, mobile workspace with a visible status board and writable surfaces; place the scrum master and product owner near the team for seamless communication.