Agile Advanced: Agile Program Management+Manager in Scrum

Define the learning objectives for agile scrum in advanced software development and program management, outlining goals for mastering scrum practices, project coordination, and strategic delivery.

Explore how understanding another methodology, such as waterfall, reveals the benefits and pitfalls of scrum from the team and project lifecycle perspectives.

Get hands-on scrum project experience and reassess your values by comparing scrum with other methodologies, then coach others using insights from early stand-ups, pair programming, and weekly iterations.

Become a certified scrum master by completing official training and passing the exam. Choose between Scrum Alliance CSM or Scrum.org PSM, with training around $1,000 or $100 exam.

Put your certified scrum master knowledge into practice by persuading peers and managers to adopt scrum, maintain its rules, and deliver tested code deployed to staging in a self-organizing team.

Voluntarily assume a leadership role as scrum master through servant leadership, coaching on rules, asking the right questions, setting an example, and empowering teams to organize and deliver.

Show depth of scrum knowledge by reading the scrum guide, applying practices in real projects, and updating a cv to scream scrum master while coaching product owners and building backlog.

Adhere to the scrum rules despite deadlines and reluctance, strengthening your character as a scrum master and delivering value through disciplined practice.

Outline the learning objectives for agile scrum advanced software development and program management. Identify the target outcomes and skills students will master.

Explain why scrum works and influence teams by addressing emotional and real-world challenges, guiding a change in how we deliver projects and improve efficiency.

Explain why agile principles work by highlighting iterative delivery, transparency, inspection, and adaptation within Scrum, with backlog-driven sprints, early testing, customer collaboration, and accountable teams.

The lecture explains five reasons the scrum master role works: it removes impediments, coaches impartially, ensures scrum rules, prevents a single point of control, and enables the team to deliver.

Explain how the product owner role drives value by turning business objectives into a prioritized requirements backlog and maximizing return on investment as the single interface between business and team.

Explore why the development team role works by highlighting cross-functional, self-organizing scrum teams of 5–9 domain experts who adapt to business needs for lean, scalable, high-quality delivery.

Explore how a centralized, visible product backlog of feature cards with acceptance criteria drives consistent prioritization. Learn how easy maintenance, stakeholder access, and change-ready flow keep backlog useful.

The definition of done in Scrum creates ownership through early team buy-in, serves as a sprint-end quality check, and ensures ship-ready software at the end of each iteration.

Learn six reasons sprint planning works, including collaborative estimation, shared understanding from the team and product owner, planning poker, and strict time boxes that align backlog with customer needs.

Explore seven reasons why the sprint works, from delivering working software within a four-week cycle to maintaining focus, certainty, and early return on investment.

Explore eight reasons the daily scrum, a strict 15-minute standup that coordinates development teams and keeps the sprint burn down chart and task board visible, boosts collaboration and issue resolution.

Burn down charts monitor progress by showing work remaining vs time, using sprint and release burn downs, update by cross or dot, reveal impediments, and motivate the team toward on-track performance.

Collaborate through backlog grooming to add, remove, amend, or split story cards with the development team, aligning product owner and team knowledge to reduce unready features in sprint planning.

Show how sprint review demonstrates working software through a product increment demo to the product owner and stakeholders, enabling feedback, backlog adaptation, and a business decision point.

Explain why the sprint retrospective works by inspecting and adapting after each sprint, as the team discusses successes and improvements, shares concerns, and boosts transparency for the next sprint.

Explore how a Scrum master leads sprint planning, user stories, and acceptance criteria with a new team in a case study of Scrum gone bad, highlighting timeboxing and facilitation lessons.

Focus on learning objectives for agile scrum in advanced software development and program management. Define clear objectives to guide learners through the course.

scale scrum to coordinate multiple teams and synchronize projects across a company. learn the scrum of scrums technique, its benefits, do's and don'ts, and practical tips from an industry expert.

Scaling scrum challenges arise when teams exceed nine members, but scrum of scrums helps deliver faster with larger initiatives while preserving rules like product backlog management and owners' prioritization.

Explore how the scrum of scrums coordinates many interrelated scrum teams through representatives, enabling scalable planning, sharing progress, identifying blockers, and preventing cross-team bottlenecks.

Adopt a four-question agenda—accomplishments since last meeting, goals before next, blockers, and potential impediments—time-boxed to 30 minutes weekly and 15 minutes daily.

Explore scrum of scrums meeting types and how coordinating multiple teams, internal or third party, with aligned roadmaps increases cross-project shippable increments.

Clarify who hosts the scrum of scrums and who to invite, designating the scrum master or program manager as host to align inter-project progress, priorities, and impediments across backlogs.

Vary the frequency of scrummage meetings based on sprint length and impediments, using daily meetings for highly complex, one to two week sprints and less frequent check-ins for longer sprints.

Lessons from industry stress time-boxed scrums, the right attendees (scrum master and product owner), and skilled hosting to keep backlog focus and maximize value.