Agile Basics for Developers, Scrum Masters & Product Owners

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

Explore how agile teams achieve collaboration and cohesion by aligning core roles: developer/tester, scrum master, product owner, with SMEs and stakeholders to deliver working software.

In the daily scrum, developers, testers, Scrum Master, and product owner bond, surface impediments, offer and seek help, and track progress toward the sprint goal and product backlog.

The product owner and stakeholders demonstrate the product increment and review what was shipped in the sprint review, while defining the definition of done and previewing the next backlog.

Explore sprint retrospective as a key scrum practice focusing on people, relationships, and processes to drive continuous improvement; assess tools, definition of done, velocity, and story points.

Scale agile beyond scrum for larger teams by exploring the Spotify model and SAFe. Examine the business case of agile for developers, scrum masters, and product owners.

Explore the Spotify model for scaling agile in enterprises, featuring squads, tribes, product areas, and product domains, plus chapters, alliances, and guilds that maintain nimbleness and develop skills.

Explore how Safe scales agile across enterprise by aligning four scrum teams to plan increments, demonstrate to stakeholders, and release via agile release trains for continuous improvement.

Explore three career paths for engineers: product firms building widely used software, IT divisions of enterprises, and IT service providers that serve both product firms and enterprises.

Develop coding mastery across languages, grasp business/product domain context, and apply hardware-aware design with leadership soft skills to excel in agile, rapid experimentation environments.

Embrace continual learning over fixed knowledge and hubris, moving through unconscious and conscious incompetence to conscious and unconscious competence, to stay open in agile practice.

Express ideas clearly in agile conversations by shedding inhibition and speaking sincerely, only when you have knowledge or a genuine question, not to hastily impress.

Develop assertiveness without arrogance to express viewpoints clearly in agile engineering. Learn to hold strong opinions loosely, listen openly to better points, and balance ego with vulnerability.

Enhance communication by balancing formal courses with inspiration from others; learn to paraphrase questions, tell stories, and respond sincerely to foster agile collaboration.

Develop collaboration in agile by practicing helping and seeking help with empathy, appropriate intervention, and clear, assertive communication; master six life and leadership skills for effective software delivery.

Learn how to handle being pushed to do more work in a sprint when it feels infeasible, by outlining your thought process and planned communication in 3–5 bullet points.

Read and respond to the second assignment, participate in review and comments, and decide how to share an important point in the daily scrum despite discomfort to help the team.

Assess capacity and environment constraints behind slow delivery and identify blockers in development and testing to inform a collaborative plan for resolution with the scrum master, coach, and product owner.

Read and respond to the assignment in the assignment section, then review and comment. Then present concise bullet points on the impact of large language models (lm) in bank chatbots.

Navigate an agile environment by committing to delivery with coding excellence and leadership. Develop six growth skills—comfortable in your skin, continuous learning, respectful expression, reasoned assertiveness, openness, and empathetic teamwork.

Engineers evolve into the Scrum Master role by embracing essential leadership skills. Module four focuses on the leadership capabilities required to excel as a Scrum Master.

Develop team dynamics by understanding each member as a person, recognizing backgrounds and competencies, practicing cognitive and affective empathy, and enabling the team while managing conflicts as a Scrum Master.

Develop strategic thinking by applying inside, around, and outside the box approaches to remove hurdles and solve problems in agile teams, using the Fosbury flip analogy.

Assume the role of scrum master to understand your team members by reviewing the first assignment and responding with comments in the assignment section.

Learn to address stakeholder communication issues in the third assignment, guiding developers and testers who appear busy or tough, as part of scrum master duties.

Review the sprint outcomes and four themes—long hours, testing capacity, infrastructure as code and containerization challenges, and a last-minute security fix—and plan actions to prevent recurrence in the next sprint.

Examine how a Scrum Master, as a servant leader, handles engineer complaints, weighing follow or break the book, and presenting three options with pros, cons, and a recommended choice.

Develop leadership as a scrum master by coaching and enabling, mastering five skills: see the big picture, build empathy, remove barriers, own the sprint retrospective, and balance enforcement with facilitation.

Define the shift from business analyst to product owner in agile, embracing delivery ownership across sprints and developing essential leadership competencies.

Develop strong stakeholder relationships by mastering emotional quotient, self-awareness, and listening to understand others' motives. Build human-centered collaboration beyond transactions to drive product strategy.

Develop strong business acumen by understanding the domain and core business model, not just user requirements, to connect dots and drive innovation as a product owner.

Prioritize effectively in agile by putting first things first, building business acumen, using a decision framework, validating with stakeholders, and clearly communicating priorities to developers and testers.

Take ownership as the attitude that any failure is on me and any success is on the team. Prioritize what matters, safeguard team well-being, and deliver business value.

Start by completing assignments to determine how you prioritize actions in a perfection-driven organization like Apple. Make assumptions, communicate your points in the assignment section, and prepare to respond.

Respond to the second assignment, review comments, explain the e-commerce business, and identify the critical modules.

Assess and respond to the assignment by examining why the team failed to deliver the product increment, holding the product owner accountable, prioritizing correctly, and outlining steps to prevent recurrence.

Identify a customer experience issue and articulate how two e-commerce features, search and payment, can improve it. Communicate the proposed improvements clearly to developers and testers.

Analyze two strong relationships and two weaker ones, examine why some relationships are strong and others are not, and propose actions to improve the weaker relationships.

Develop ownership and strategic thinking as a product owner by building relationships, applying business acumen, and mastering persuasive communication to deliver continuous business value while preventing burnout.

Explore how DevOps bridges development and IT operations within agile teams, outlining roles of developers, testers, scrum masters, and product owners in delivering scalable production environments.

Dev pursues change and innovation, while ops prioritizes reliability and service delivery. The wall of confusion challenges teams as they balance speed with stability.

Navigate the wall of confusion between development and operations by contrasting agile sprint activities—plan, code, build, test, release—and operations' focus on stability, SLAs, and incidents.

DevOps is an inseparable twin to agile, reducing friction between dev and ops while enabling faster, stable deployments through automation, feature switches, A/B testing, and kanban.

DevOps Camp fosters a non-blaming, collaborative culture between development and operations to deliver value faster. It emphasizes automation, metrics, and knowledge sharing through provisioning, testing, containerization, and cross-team collaboration.

Discover how to automate the DevOps pipeline from planning and coding to building, testing, deploying, and monitoring, using continuous integration with tools like Jenkins for self-service deployment.

Explore DevOps as an inseparable twin to agile, presented as a teaser rather than a dive. Learn leadership skills developers, scrum masters, and product owners need to deliver value faster.

Explore core agile concepts, the business case for agile, and leadership roles of developers, testers, scrum masters, and product owners, with nods to devops and methods like Spotify and Safe.

Time to market drives revenue, while agile accelerates feature delivery. It enables customer experience management by testing, launching, measuring, and pivoting to deliver business value and adapt to change.

Strengthen leadership for developers and testers by mastering the clear framework—confidence, learning, express, assert, and respectful communication—while embracing continuous learning and nuanced, effective communication.

The scrum master acts as an enabler, coach, and motivator who empowers developers and removes hurdles, guiding with the beacon framework: empathy and teamwork, creative initiatives, orchestration, and nuanced management.

Developers should embrace agile behaviors aligned with business imperatives, cultivate leadership and soft skills across roles, and pursue a mindset of continuous improvement with ownership of solutions.