Scrum PSPO I and Go: Your Roadmap to Agile Mastery
Scrum is not just a methodology; it is a way of thinking that reshapes how people collaborate, deliver products, and confront change. The foundation of Scrum lies in its ability to transform uncertainty into opportunity through transparency, inspection, and adaptation. The framework enables teams to handle complexity with agility, turning intricate problems into manageable increments of work. It redefines the nature of teamwork by focusing on empirical process control, which ensures decisions are made based on observation and experimentation rather than assumptions. This principle alone makes Scrum a powerful mechanism for achieving sustainable development in today’s fast-evolving business environments.
The story of Scrum begins in the realm of software development, yet its influence now transcends industries, guiding everything from healthcare innovation to marketing operations. Scrum thrives on collaboration and responsiveness. At its heart are small, cross-functional teams empowered to self-organize, continuously refine their work, and deliver value in short, repeatable cycles known as sprints. Each sprint is a miniature project of its own—planned, executed, and reviewed—producing a usable increment of the product. This cyclic rhythm of work promotes transparency and allows stakeholders to visualize progress in real time. As a result, organizations can pivot swiftly in response to feedback, emerging trends, or unforeseen challenges.
Central to Scrum is the concept of empiricism. The framework relies on what is known, what can be observed, and what can be verified through experience. Every element in Scrum exists to support this approach. Transparency ensures that all aspects of the process are visible to those responsible for the outcome. Inspection provides frequent evaluation of progress toward a goal, while adaptation enables the team to adjust course when deviations occur. This cycle of learning creates a continuous feedback loop that refines both the product and the process. Rather than prescribing detailed steps, Scrum defines boundaries within which creativity can flourish.
Scrum consists of three primary roles: the Product Owner, the Scrum Master, and the Developers. Each role has a distinct purpose but shares the same ultimate goal—delivering valuable outcomes. The Product Owner represents the voice of the customer and ensures that the team is always working on the most valuable features. In the context of PSPO I, or Professional Scrum Product Owner I, this role is particularly significant because it connects business strategy to product execution. The Product Owner manages the product backlog, prioritizes items based on value and risk, and communicates a clear vision that inspires the development team. Through effective backlog management, the Product Owner transforms abstract ideas into tangible goals aligned with business objectives.
The Scrum Master, on the other hand, acts as a servant-leader who nurtures the team’s understanding of Scrum principles. Their primary duty is to remove impediments that hinder progress, ensuring the team can work at its optimal pace. They foster an environment of trust, where experimentation is encouraged and failure is treated as a learning opportunity. The Scrum Master also protects the team from external disruptions and facilitates the key Scrum events—Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective—ensuring that each event fulfills its purpose. The Developers, meanwhile, are responsible for converting the prioritized product backlog items into usable increments during each sprint. They decide how to accomplish the work, reinforcing Scrum’s commitment to self-organization and accountability.
Scrum’s minimal structure is what makes it both lightweight and powerful. It consists of only a few artifacts and events, yet it creates a rhythm that guides teams toward continuous improvement. The artifacts—Product Backlog, Sprint Backlog, and Increment—represent the evolving state of work. The Product Backlog is a dynamic list of everything that might be needed in the product, constantly refined as priorities change. The Sprint Backlog is a subset of that list, chosen for completion during a sprint. The Increment is the sum of all completed work that meets the Definition of Done. These artifacts offer transparency, allowing everyone to see what is planned, what is in progress, and what has been accomplished. The Scrum events, held regularly and time-boxed, bring discipline to the process without adding unnecessary rigidity.
Scrum’s strength lies in its adaptability. Unlike traditional project management methods, which often rely on predictive planning and sequential phases, Scrum embraces uncertainty as a constant companion. The world rarely unfolds exactly as planned, and Scrum acknowledges this reality by promoting iterative development. Each sprint becomes an opportunity to gather insights, test hypotheses, and refine both the product and the process. This iterative rhythm minimizes risk because feedback is incorporated continuously rather than deferred to the end of a long project. The result is a more responsive and resilient approach to delivering value.
The PSPO I certification reflects a deep understanding of these principles from the Product Owner’s perspective. A certified Product Owner must grasp not only the mechanics of Scrum but also the economics of product development—how to maximize return on investment through smart backlog prioritization. They are accountable for ensuring that the product delivers measurable value to stakeholders. Their decisions shape the trajectory of the product, influencing its design, functionality, and ultimate success. By focusing on outcomes rather than outputs, the Product Owner ensures that every increment produced by the team contributes meaningfully toward the overall vision. In many ways, the Product Owner is the strategic heartbeat of Scrum, balancing innovation with practicality.
Scrum’s simplicity often masks the depth of discipline it demands. Teams new to Scrum may initially view it as a set of meetings and roles, but as they dive deeper, they uncover the profound mindset shift it requires. Transparency demands honesty about progress and problems alike. Inspection requires critical thinking and a willingness to confront uncomfortable truths. Adaptation necessitates humility—the recognition that plans may need to change. Together, these principles cultivate a culture of continuous improvement. This cultural transformation is what distinguishes organizations that merely adopt Scrum from those that truly live it.
A crucial element of Scrum’s success is communication. The framework thrives on open dialogue, frequent feedback, and shared understanding. The Daily Scrum, often a short meeting each day, is not about status reporting but synchronization. It allows team members to align their work and surface impediments early. The Sprint Review invites stakeholders to inspect the increment and offer insights, ensuring that the product evolves in line with expectations. The Sprint Retrospective is a dedicated moment for reflection, where the team examines how it works and commits to actionable improvements. Through these interactions, Scrum fosters a rhythm of collaboration that drives quality and innovation.
One of the most misunderstood aspects of Scrum is its relationship with predictability. Critics sometimes argue that Scrum’s iterative nature makes long-term planning difficult, but in reality, it enhances predictability through regular delivery and transparency. Because progress is visible after every sprint, stakeholders can make informed decisions about scope, timelines, and budgets. The frequent inspection of increments ensures that deviations are detected early, reducing the risk of large-scale failure. This empirical approach aligns perfectly with the complexity of modern projects, where uncertainty is the norm rather than the exception.
Scrum also brings a human dimension to work that traditional frameworks often neglect. Empowering teams to make decisions and self-organize stills a sense of ownership and motivation. People feel more connected to the outcome because they directly influence it. The role of leadership in Scrum shifts from command and control to guidance and support. This transformation not only enhances productivity but also nurtures creativity and morale. In environments where change is constant, such intrinsic motivation becomes a critical advantage.
Implementing Scrum, however, is not without its challenges. Many organizations struggle in the transition from hierarchical structures to empowered teams. Resistance often arises from a desire for certainty and control, yet Scrum asks leaders to trust the process and the people. Success with Scrum depends on a shared commitment to its principles. Merely performing the ceremonies without embracing the underlying values leads to what practitioners call “mechanical Scrum,” where the form is present but the spirit is absent. True agility emerges only when teams internalize the values of courage, focus, commitment, respect, and openness.
Scrum’s growing relevance across industries reflects its universality. Whether building a digital product, coordinating a marketing campaign, or designing a physical product, the framework offers the same promise—delivering incremental value while embracing change. It provides a structure that balances flexibility with discipline, empowering teams to innovate without losing direction. For individuals pursuing PSPO I certification, understanding this universality is crucial. The principles they learn are not confined to software development; they apply wherever complex work requires collaboration and adaptability.
The enduring strength of Scrum lies in its community. Over decades, practitioners around the world have contributed to refining its practices, sharing insights, and evolving its application. This global exchange of knowledge ensures that Scrum remains relevant even as technologies and markets evolve. The PSPO I certification represents not just an individual’s mastery of concepts but a connection to this larger network of professionals committed to improving how people work together. It signifies a mindset that values empirical learning, continuous improvement, and customer-centric innovation.
Scrum is more than a framework; it is a philosophy of work. It teaches that progress comes not from rigid adherence to plans but from adaptive learning. It shifts focus from tasks to value, from control to collaboration, from prediction to discovery. In a world defined by volatility and rapid change, these lessons are invaluable. Teams that internalize them become more resilient, creative, and effective. For those embarking on the PSPO I journey, understanding these foundations is the first step toward becoming not just a Product Owner, but a steward of value creation. The journey begins with mastering the fundamentals, but it extends into a lifelong pursuit of excellence, adaptability, and purpose. Scrum offers the compass; it is up to each practitioner to chart the course.
The Product Owner is the linchpin of Scrum, bridging the gap between stakeholders and the development team. This role demands clarity, strategic thinking, and an unwavering focus on maximizing value. Unlike traditional project managers who often oversee execution, the Product Owner defines what should be built, why it matters, and in what order. They act as the voice of the customer, translating vision, business priorities, and user needs into actionable items for the team. Their decisions shape the product trajectory, influence market relevance, and determine how quickly organizations can respond to change. The role embodies both responsibility and opportunity, offering the chance to guide the creation of products that genuinely solve problems.
At the heart of the Product Owner’s work is the product backlog. This evolving list of features, improvements, fixes, and technical work is the primary instrument for directing team efforts. The Product Owner prioritizes the backlog based on value, risk, dependencies, and feedback from stakeholders. This prioritization is not arbitrary; it requires careful analysis of customer needs, market trends, and organizational goals. Each backlog item represents a small hypothesis: a potential increment of value that can be tested, delivered, and refined. The backlog is dynamic, growing, and changing as new information emerges. The ability to manage this flux effectively distinguishes great Product Owners from average ones.
The Product Owner must also communicate a compelling vision. This vision serves as a compass for the team, guiding their decisions, choices, and creative solutions. A well-articulated vision is more than a statement; it is an ongoing narrative that aligns stakeholders, inspires developers, and sets expectations for the end product. Within the PSPO I framework, understanding how to craft and sustain this vision is crucial. It involves balancing ambition with feasibility, clarity with adaptability, and strategic objectives with immediate deliverables. The vision is not static; it evolves alongside the product, providing context for each sprint and increment.
One of the most critical aspects of the Product Owner role is stakeholder engagement. Effective Product Owners continuously interact with users, customers, executives, and other teams. They gather insights, solicit feedback, and ensure that the product is aligned with real-world needs. This engagement is not a one-time activity; it is continuous, iterative, and embedded in every stage of product development. By maintaining open channels of communication, the Product Owner ensures that decisions are informed, priorities are validated, and surprises are minimized. The ability to synthesize diverse perspectives into a coherent backlog is a mark of expertise in this role.
Decision-making is another cornerstone of the Product Owner’s responsibilities. Every choice—from feature prioritization to release timing—has implications for value creation, risk management, and customer satisfaction. Product Owners must weigh trade-offs, anticipate consequences, and act decisively while remaining flexible. This requires a combination of analytical skill, intuition, and empathy. Understanding which features drive business outcomes, which enhancements improve user experience, and which technical investments reduce future cost is central to effective product ownership. The PSPO I framework emphasizes these skills, highlighting their importance in delivering products that matter.
The Product Owner’s collaboration with the development team is unique. Unlike a traditional manager who dictates tasks, the Product Owner presents the what and why while trusting the team to determine the how. This empowers developers, fosters creativity, and reinforces the principles of self-organization. Collaboration is built on trust, clarity, and continuous dialogue. Developers need to understand the context of backlog items, their relative priority, and the business rationale behind each choice. When this understanding is shared, teams can make informed trade-offs, identify risks early, and propose innovative solutions. The Product Owner is a partner, facilitator, and sometimes challenger, encouraging the team to achieve the best possible outcomes.
Sprint planning is a vital event where the Product Owner’s role becomes highly visible. During planning, the Product Owner communicates the highest-priority items and ensures that the team understands the goals for the sprint. While they do not dictate how the work is completed, their input shapes the team’s focus and informs decision-making about scope and sequencing. By clarifying expectations, answering questions, and providing context, the Product Owner enables the team to commit to work confidently. This interaction exemplifies Scrum’s balance between direction and autonomy, demonstrating how empowerment and alignment coexist in practice.
Another essential responsibility is ensuring transparency of progress. The Product Owner tracks delivery, monitors backlog evolution, and communicates progress to stakeholders. They provide insights into which items have been completed, which are in progress, and which require attention. Transparency is critical not only for maintaining trust but also for enabling rapid adaptation. By having a clear understanding of what has been achieved and what remains, stakeholders can make informed decisions, teams can adjust priorities, and organizations can respond more effectively to market dynamics. This visibility is a hallmark of successful Scrum implementation.
The Product Owner must also embrace feedback loops as a core component of their role. Feedback can come from customers, analytics, testing, or the development team itself. It is the Product Owner’s responsibility to integrate this feedback into backlog refinement, ensuring that the product evolves toward higher value. A backlog that ignores feedback becomes stagnant and misaligned with actual needs. Scrum encourages the Product Owner to treat each sprint as an experiment, testing hypotheses about value creation and learning from outcomes. This iterative, empirical approach is central to both Scrum and the PSPO I philosophy.
Effective Product Owners are also adept at balancing competing priorities. They must reconcile the sometimes conflicting interests of business stakeholders, users, and technical constraints. Decisions are rarely simple; they involve trade-offs, compromise, and negotiation. The Product Owner must maintain a clear focus on value while considering the broader organizational strategy. In doing so, they protect the team from being overburdened by unnecessary tasks, ensure alignment with business goals, and guide the product toward meaningful outcomes. This balancing act requires diplomacy, insight, and resilience.
The impact of a Product Owner extends beyond backlog management and sprint planning. By consistently prioritizing value, facilitating communication, and fostering alignment, they influence organizational culture. Teams learn to focus on outcomes rather than outputs, stakeholders learn to engage constructively, and leadership gains confidence in the empirical process. The Product Owner becomes a catalyst for organizational agility, demonstrating how strategic clarity and tactical execution intersect. In many ways, the effectiveness of Scrum in any organization can be traced back to the capabilities of its Product Owner.
Scrum also emphasizes measurable outcomes. Product Owners define success not by completed tasks alone but by the value delivered to users and the organization. This involves setting goals, identifying metrics, and evaluating results. Metrics such as user adoption, revenue impact, or cycle time provide objective insights into progress. By grounding decisions in measurable results, the Product Owner ensures that the team remains focused on producing meaningful impact. The PSPO I framework underscores this focus on value and metrics, guiding Product Owners to operate with both vision and accountability.
While the responsibilities are extensive, effective Product Owners thrive by embracing the iterative nature of Scrum. Each sprint offers opportunities to reassess priorities, refine strategies, and learn from outcomes. By approaching their work as a continuous cycle of observation, learning, and adaptation, Product Owners cultivate resilience and foresight. They understand that perfection is neither attainable nor desirable; instead, progress is achieved through incremental improvements and responsive decision-making. This mindset distinguishes high-performing Product Owners from those who merely execute tasks.
Finally, the role requires continuous personal development. Product Owners must remain attuned to market trends, user expectations, and advancements in agile practices. They cultivate skills in communication, negotiation, analysis, and leadership. The PSPO I certification represents one milestone in this journey, providing foundational knowledge, practical frameworks, and strategies for managing the product role effectively. Beyond certification, ongoing learning, reflection, and application are essential to maintaining excellence in a rapidly evolving environment.
The Product Owner is a linchpin in Scrum, integrating strategy, execution, and feedback to maximize value. Their work shapes the product, guides the team, and influences the organization. Through careful backlog management, clear vision, stakeholder engagement, and iterative learning, the Product Owner transforms ideas into actionable outcomes. Mastery of this role requires discipline, insight, empathy, and an unrelenting focus on delivering value. The PSPO I framework provides the knowledge and principles to succeed, but real-world practice, adaptation, and continuous improvement define excellence. The Product Owner is not merely a role to fill; it is a responsibility to embrace, a position to lead with vision, and an opportunity to shape meaningful change.
Scrum is a framework built for agility, enabling teams to navigate complexity while delivering valuable outcomes. It is designed around the principles of empirical process control, which emphasizes transparency, inspection, and adaptation. These principles allow teams to make informed decisions based on observable evidence rather than assumptions. Each element of Scrum, from roles to artifacts to events, exists to support these principles and facilitate the creation of high-value products. Mastering Scrum requires understanding how these components interrelate and how they guide teams toward consistent delivery and continuous improvement.
At the center of Scrum is the concept of the sprint, a time-boxed iteration during which a potentially shippable increment of work is produced. Sprints are usually one to four weeks long, providing a rhythm that drives predictability and focus. Unlike traditional projects, which often operate with a linear, sequential approach, sprints allow teams to deliver work incrementally. Each sprint begins with planning, during which the team selects high-priority items from the product backlog and determines how they will transform them into a usable increment. The selection process is guided by the Product Owner, who ensures alignment with value creation and stakeholder priorities. The development team retains autonomy over execution, deciding how to implement the work efficiently and effectively.
The sprint itself is a period of concentrated effort, where transparency and collaboration are critical. Daily scrums, short stand-up meetings, provide a mechanism for inspection and adaptation, allowing the team to assess progress, identify obstacles, and coordinate work. These daily interactions reinforce accountability, facilitate problem-solving, and maintain alignment with the sprint goal. Beyond the team, stakeholders rely on the sprint cycle to gain visibility into progress, providing opportunities for feedback and early course correction. The iterative nature of sprints ensures that learning occurs continuously, reducing risk and increasing the likelihood of delivering valuable outcomes.
Scrum artifacts play an equally critical role in guiding work and maintaining transparency. The product backlog is the single source of truth for all potential work. It is dynamic, evolving as new insights, opportunities, and requirements emerge. Each backlog item represents a hypothesis about delivering value, and the Product Owner prioritizes these items based on their anticipated impact, risk, and cost. Backlog refinement is an ongoing activity, ensuring that items are sufficiently clear, estimated, and prioritized before they are considered for a sprint. The artifact’s transparency allows stakeholders and teams to maintain a shared understanding of what is planned and why it matters.
The sprint backlog is a subset of the product backlog, selected for a specific sprint. It represents the team’s commitment to delivering a usable increment. Unlike the product backlog, which is a living document influenced by multiple factors, the sprint backlog is a tactical plan focused on immediate execution. It includes not only the items to be completed but also the plan for achieving them, allowing the team to manage work in a self-organized manner. Daily scrums and other interactions help the team adjust the plan as obstacles arise, reinforcing Scrum’s empirical nature. The sprint backlog demonstrates how Scrum balances structure with flexibility, providing clarity while empowering the team to determine the best path forward.
The increment is the most tangible artifact, representing the sum of all completed backlog items that meet the definition of done. Each increment is a step toward the product vision, providing real-world feedback and measurable outcomes. Delivering increments frequently ensures that stakeholders can validate assumptions, discover new requirements, and adjust priorities accordingly. This approach reduces the uncertainty inherent in complex projects, allowing teams to course-correct continuously. For Product Owners pursuing PSPO I certification, understanding the increment is essential, as it is the primary mechanism through which value is measured and realized.
Scrum events are structured to maximize transparency, inspection, and adaptation while avoiding unnecessary overhead. Sprint planning sets the stage by aligning the team on goals, backlog items, and execution strategies. The daily scrum provides a rhythm for coordination and problem-solving. The sprint review engages stakeholders, showcasing the increment and collecting feedback to inform future backlog decisions. The sprint retrospective allows the team to reflect on their processes, identifying improvements and committing to actionable changes. Together, these events create a feedback loop that strengthens team performance, aligns priorities, and maintains focus on value creation.
Empiricism is the backbone of Scrum. By relying on observable outcomes rather than predictions, teams can navigate uncertainty with confidence. Every increment, every backlog refinement, and every feedback session provides data that informs decisions. This empirical approach fosters a culture of learning, where experimentation is encouraged, mistakes are seen as opportunities for growth, and continuous improvement is the norm. Product Owners must embrace this mindset, leveraging feedback to prioritize backlog items and guide the team toward delivering the highest possible value. PSPO I emphasizes this principle, teaching practitioners to manage uncertainty proactively and make informed decisions.
Scrum also emphasizes the human element of teamwork. Self-organization and collaboration are critical to success. Development teams are empowered to determine how to accomplish work, fostering creativity and ownership. The Scrum Master facilitates this process, protecting the team from disruptions, coaching them in Scrum practices, and promoting a culture of accountability. The Product Owner complements this by providing strategic guidance, maintaining focus on value, and ensuring stakeholder alignment. This interplay between autonomy and guidance is what enables Scrum teams to perform at a high level, even in complex and rapidly changing environments.
Prioritization is a continuous responsibility for the Product Owner. Not all work delivers equal value, and decisions about what to do first have profound implications for business outcomes. Effective prioritization involves assessing risk, business impact, technical complexity, and feedback from users and stakeholders. Each decision shapes the product incrementally, aligning it more closely with customer needs and organizational goals. In this way, the backlog becomes a living representation of the organization’s evolving strategy, with each item reflecting a conscious choice to maximize value and minimize waste. PSPO I certification emphasizes techniques for achieving effective prioritization, combining analytical skill with practical insight.
Scrum’s iterative nature enables experimentation and adaptability. Teams can test ideas, deliver them quickly, gather feedback, and refine them in subsequent sprints. This approach contrasts sharply with traditional methods, where work is planned and executed in long, rigid cycles, and mistakes are often costly. Scrum reduces risk by breaking work into increments, allowing for learning and adjustment throughout the project. The feedback loop created by sprints, reviews, and retrospectives ensures that decisions are grounded in reality, not speculation. It also promotes a mindset of continuous improvement, where teams seek to learn, optimize, and enhance their performance over time.
The role of the Product Owner is inseparable from the framework itself. By maintaining a clear vision, prioritizing backlog items, and engaging stakeholders, the Product Owner ensures that each sprint contributes meaningfully to the overall product. They act as a custodian of value, constantly assessing whether work aligns with business objectives and user needs. Their decisions influence the allocation of resources, the direction of the product, and the pace of delivery. In essence, the Product Owner translates strategy into actionable goals, guiding the team while respecting its autonomy and expertise.
Scrum’s transparency is essential for trust and accountability. All artifacts and events are designed to make work visible, progress measurable, and impediments apparent. Transparency allows stakeholders to understand priorities, track progress, and provide informed feedback. It also enables teams to inspect their work and adapt processes, fostering a culture of openness and learning. Without transparency, Scrum cannot achieve its intended purpose, as decisions would rely on assumptions rather than empirical evidence. Product Owners, Scrum Masters, and development teams must collaborate to maintain this transparency consistently, ensuring that every action supports value creation.
Continuous improvement is both a goal and a process in Scrum. Retrospectives, feedback loops, and metrics provide teams with the data needed to enhance performance. Product Owners use these insights to refine backlog prioritization, clarify requirements, and adjust strategies. Development teams apply lessons learned to improve collaboration, technical practices, and workflow efficiency. Scrum Masters facilitate this process by guiding reflection and helping teams implement changes. Over time, this cycle of inspection and adaptation builds organizational resilience, fostering a culture where learning, innovation, and responsiveness are natural behaviors.
Scrum’s simplicity is its greatest strength. Its framework is lightweight, yet it supports complex decision-making and dynamic execution. By defining roles, events, and artifacts while leaving flexibility in how work is accomplished, Scrum empowers teams to respond effectively to uncertainty. The Product Owner, as a central figure in this ecosystem, ensures that strategic intent and practical execution remain aligned. Through careful backlog management, effective stakeholder engagement, and adherence to empirical principles, the Product Owner maximizes the value delivered by the team while maintaining focus on the long-term vision.
The framework also encourages a focus on value rather than output. Traditional project management often measures success by tasks completed or hours logged. Scrum shifts the perspective to outcomes and impact, asking whether the work done truly serves the customer and organization. The Product Owner guides this focus, using feedback, metrics, and insight to prioritize work that generates meaningful results. In doing so, Scrum ensures that resources are invested wisely, risks are managed proactively, and every increment contributes to tangible value. PSPO I certification reinforces this principle, emphasizing the importance of value-driven decision-making and outcome-oriented leadership.
Scrum’s iterative, empirical, and human-centered approach equips organizations to thrive in volatile, uncertain, complex, and ambiguous environments. By delivering work incrementally, inspecting progress frequently, and adapting to feedback, teams maintain alignment with evolving needs. The Product Owner plays a crucial role in this process, connecting strategy to execution, ensuring prioritization aligns with value, and engaging stakeholders effectively. Mastery of Scrum, therefore, requires more than procedural knowledge; it demands a mindset attuned to learning, collaboration, and continuous improvement. PSPO I serves as a foundation for developing this mindset, equipping practitioners with the tools and insights needed to navigate complexity with confidence.
Scrum is more than a framework; it is a philosophy for creating high-value products in a complex world. Its principles guide behavior, decisions, and interactions, ensuring that teams deliver meaningful outcomes while remaining flexible and responsive. The Product Owner, supported by the Scrum Master and development team, ensures that the framework achieves its purpose: transforming strategy into usable, valuable increments. By embracing empirical process control, fostering transparency, prioritizing value, and promoting continuous improvement, organizations can unlock the full potential of Scrum, delivering products that matter to both customers and business stakeholders.
Scrum is a framework that thrives on practical application, translating theory into consistent delivery of high-value products. While its principles are deceptively simple, its true power emerges when teams fully embrace the interplay of roles, events, and artifacts. In practice, Scrum is more than a project methodology; it is a way of thinking, a lens through which work is planned, executed, and refined. Its adoption requires a shift in mindset, emphasizing collaboration, transparency, and responsiveness, qualities essential in today’s fast-paced, unpredictable environments. The roles within Scrum are carefully defined to balance accountability, guidance, and execution, ensuring that every team member contributes to value creation while maintaining a sense of shared ownership and purpose.
At the core of Scrum’s operational structure are three key roles: the Product Owner, the Scrum Master, and the Development Team. Each role carries distinct responsibilities, yet the framework relies on the synergy among these roles to achieve optimal results. The Product Owner acts as the custodian of value, responsible for managing the product backlog and ensuring that every backlog item contributes meaningfully to the overall product vision. This requires constant engagement with stakeholders, a deep understanding of customer needs, and the ability to prioritize effectively. For those pursuing PSPO I certification, mastery of backlog management, value assessment, and stakeholder alignment is crucial. The Product Owner’s decisions directly influence the team’s focus, the product’s evolution, and ultimately, the business outcomes.
The Scrum Master serves as a facilitator, protector, and coach, guiding the team in the proper application of Scrum principles. Their primary role is not to manage the team in a traditional sense, but to enable self-organization, remove impediments, and foster a culture of continuous improvement. The Scrum Master helps the team navigate challenges, ensuring that interactions, processes, and artifacts maintain clarity and purpose. They also act as a bridge between the team and external stakeholders, defending the team from unnecessary interruptions while advocating for transparency. Effective Scrum Masters cultivate an environment where experimentation, reflection, and learning are encouraged, which is essential for achieving sustainable high performance.
The Development Team is the engine of Scrum, responsible for transforming backlog items into usable increments of the product. Teams are cross-functional and self-organizing, meaning they possess all the skills necessary to complete work independently and make tactical decisions about execution. This autonomy encourages creativity, collaboration, and accountability, as every team member understands their contribution to the sprint goal and product vision. Teams are intentionally small, typically between five and nine members, enabling effective communication, rapid decision-making, and cohesive collaboration. Within this structure, the balance between autonomy and alignment is delicate but critical; the team must be empowered to innovate while remaining focused on delivering value that meets stakeholder expectations.
The sprint, a time-boxed iteration of work, is the heartbeat of Scrum practice. It provides a predictable rhythm that allows for planning, execution, review, and adaptation. Each sprint begins with sprint planning, where the team selects high-priority backlog items and defines a sprint goal that articulates the purpose of the iteration. This goal is a guiding beacon, ensuring that all work contributes to tangible outcomes. Planning is not merely a mechanical exercise; it involves negotiation, collaboration, and foresight, balancing ambition with realism. The sprint duration, usually one to four weeks, is deliberately short to maximize feedback opportunities and minimize risk. By delivering small, usable increments at the end of each sprint, teams create a foundation for learning and adaptation, which is essential in complex, rapidly changing environments.
Daily scrums, brief meetings held at the same time each day, reinforce transparency, inspection, and adaptation. These gatherings allow the team to synchronize efforts, identify obstacles, and adjust the daily plan to ensure progress toward the sprint goal. Although the daily scrum is a simple practice, it embodies the empirical principles that underlie Scrum. It creates a continuous feedback loop, allowing the team to respond to emerging challenges and optimize performance in real time. In addition to fostering operational alignment, daily scrums enhance accountability and communication, critical components for maintaining the pace and focus required to deliver meaningful outcomes.
Scrum artifacts—product backlog, sprint backlog, and increment—serve as tangible representations of work, progress, and value. The product backlog is a dynamic list of all work items that could potentially be developed. It is continuously refined, reordered, and clarified to reflect changing priorities, stakeholder feedback, and emerging insights. The Product Owner oversees this artifact, ensuring it aligns with strategic objectives and maximizes return on investment. The sprint backlog, a subset of the product backlog selected for a specific sprint, represents the team’s commitment to achieving the sprint goal. Unlike the product backlog, which evolves, the sprint backlog provides a tactical plan for immediate execution. It is a living document, adapting to changes as the team gains new information or encounters unforeseen challenges. The increment, representing completed work that meets the definition of done, is the most concrete expression of Scrum’s value-driven philosophy. Each increment allows stakeholders to assess progress, validate assumptions, and influence future work, creating a continuous cycle of learning and adaptation.
The empirical nature of Scrum demands that decisions be based on observation and evidence rather than assumptions or predictions. Every artifact, event, and interaction serves as a data point that informs the next step. This approach reduces uncertainty, mitigates risk, and enables organizations to respond effectively to change. Product Owners must embrace empiricism by continuously validating hypotheses about value, reassessing priorities, and adapting the backlog to reflect new insights. For teams preparing for PSPO I, understanding and applying these principles is foundational. Empiricism transforms work from a linear, static process into a dynamic, iterative journey where learning drives decision-making and outcomes evolve organically.
Scrum emphasizes delivering value incrementally and frequently. This approach contrasts sharply with traditional project management methods, where large, monolithic releases often delay feedback and increase risk. By focusing on small, usable increments, Scrum allows stakeholders to interact with the product early and often. Feedback obtained through sprint reviews informs subsequent planning, helping the team refine priorities and improve product-market fit. The incremental delivery model also enhances user satisfaction, as customers experience tangible improvements regularly, rather than waiting months or years for a complete product. The Product Owner’s role in this process is to interpret feedback, reprioritize backlog items, and ensure that each increment maximizes value while minimizing waste.
Collaboration is a cornerstone of Scrum. The framework promotes open communication, shared responsibility, and mutual respect among team members. By fostering a culture of psychological safety, teams can experiment without fear of failure, surface problems without hesitation, and innovate continuously. Collaboration extends beyond the development team to include stakeholders, customers, and the broader organization. The Product Owner facilitates this engagement, ensuring that insights from diverse perspectives inform backlog prioritization and strategic decisions. In practice, collaboration is not just a method of communication; it is a mechanism for learning, alignment, and value creation, enabling teams to navigate complexity effectively.
Continuous improvement is embedded in the Scrum framework through retrospectives and iterative learning. At the end of each sprint, the team reflects on its processes, interactions, and outcomes, identifying areas for enhancement and committing to actionable changes. These reflections drive gradual, meaningful improvements in productivity, quality, and collaboration. The Scrum Master plays a critical role in guiding this process, coaching the team to adopt better practices and helping remove obstacles that impede progress. Over time, continuous improvement fosters a resilient, adaptive culture where learning, efficiency, and innovation are ingrained. For Product Owners pursuing PSPO I, understanding how to leverage retrospectives and feedback loops is essential for aligning priorities with evolving business needs and customer expectations.
Scrum also addresses the human dimension of work. Recognizing that individuals and interactions are more valuable than rigid processes or tools, the framework prioritizes engagement, empowerment, and accountability. Teams are encouraged to self-organize, make decisions collaboratively, and take ownership of outcomes. The Product Owner complements this by providing vision, guidance, and context, ensuring that the team’s autonomy operates within a strategic framework. This balance between empowerment and alignment is delicate but vital; it enables creativity and initiative while maintaining focus on delivering tangible value. In practice, the synergy between autonomy, guidance, and continuous feedback drives sustainable high performance and adaptability.
Value-driven decision-making is central to Scrum. Unlike traditional project management, which often emphasizes output or task completion, Scrum focuses on outcomes and impact. Every decision, from backlog prioritization to sprint planning, is evaluated based on its potential to deliver value to the customer and organization. This approach requires continuous assessment, stakeholder engagement, and responsiveness to changing conditions. The Product Owner’s responsibility is to ensure that resources are allocated efficiently, risks are mitigated, and every increment contributes meaningfully to strategic objectives. PSPO I certification equips practitioners with the skills to make these decisions systematically, using empirical evidence and strategic insight to maximize value.
Scrum thrives in environments characterized by uncertainty and change. By breaking work into time-boxed iterations, maintaining transparency, and leveraging empirical feedback, teams can navigate complex challenges with confidence. The framework’s adaptability allows organizations to respond to emerging requirements, shifting priorities, and unforeseen obstacles without derailing progress. This resilience is particularly valuable in today’s dynamic business landscape, where speed, flexibility, and continuous learning are essential for competitiveness. Product Owners, in their role as value stewards, are instrumental in harnessing this adaptability, ensuring that the team’s efforts remain focused on outcomes that matter most.
Scrum is more than a methodology; it is a philosophy for working in complex environments. Its focus on iterative delivery, empirical decision-making, transparency, collaboration, and continuous improvement equips teams to deliver high-value products consistently. The Product Owner, as the steward of value, ensures that every decision, priority, and increment aligns with organizational goals and customer needs. Mastery of Scrum requires both practical skill and a mindset attuned to learning, adaptation, and resilience. PSPO I certification provides a structured path to develop these competencies, enabling practitioners to guide their teams effectively, maximize value, and navigate complexity with confidence.
Scrum is a dynamic framework, and its power is realized in practice, not theory. Organizations that embrace its principles, roles, and artifacts develop a rhythm of learning and delivery that transforms how work is approached and value is created. The iterative nature of sprints, the focus on incremental progress, and the emphasis on continuous feedback create a system where teams can thrive despite uncertainty. Product Owners play a pivotal role in this system, bridging strategy and execution, prioritizing value, and engaging stakeholders effectively. By committing to Scrum’s principles, practitioners can cultivate teams and organizations capable of delivering meaningful outcomes repeatedly, learning continuously, and adapting swiftly to the demands of a complex, evolving world.
Scrum is often seen as a framework for organizing work, but at its core, it is a philosophy of understanding complexity, embracing change, and cultivating a rhythm of consistent value delivery. Its power lies not merely in the events or artifacts it prescribes but in how teams internalize its principles and live them through daily practice. The mastery of Scrum requires both discipline and a willingness to learn continuously. For Product Owners, particularly those pursuing PSPO I certification, this mastery translates into an ability to guide teams toward outcomes that maximize impact, balance priorities, and adapt intelligently to emergent circumstances. By grasping the nuances of Scrum, leaders can transform how their organizations think about work, value, and collaboration, making the framework an engine for both productivity and innovation.
Central to this mastery is the understanding that Scrum thrives in complex, adaptive environments. Unlike traditional methods that assume predictability and linearity, Scrum embraces uncertainty and change as constants. The iterative cycles of sprints, combined with empirical inspection and adaptation, provide a structured way to navigate unpredictability. Teams are encouraged to experiment, learn from outcomes, and adjust priorities based on evidence rather than assumptions. For Product Owners, this perspective demands an acute awareness of both market dynamics and customer needs, as well as the ability to translate these insights into backlog items that genuinely enhance value. Each decision becomes an opportunity to validate hypotheses, refine strategies, and ensure that the product evolves in a way that aligns with organizational goals.
The concept of value is foundational in Scrum. Every action, whether planning, developing, or reviewing, is measured against its potential to contribute to meaningful outcomes. For Product Owners, understanding value is both strategic and tactical. Strategically, value aligns with long-term organizational objectives, market positioning, and customer satisfaction. Tactically, value is expressed through incremental improvements delivered in each sprint. By focusing on high-priority features that generate tangible benefits, teams avoid the trap of producing work that looks complete but has minimal impact. Mastery of value assessment is a key competency for PSPO I candidates, requiring both analytical acumen and a deep empathy for user experience.
The Product Owner’s responsibility in Scrum is not static; it evolves as the team, product, and market evolve. This dynamic nature requires continuous engagement with stakeholders, customers, and team members. Each interaction informs backlog refinement, prioritization, and planning. The Product Owner must be adept at balancing competing demands, negotiating trade-offs, and making decisions that optimize overall value. The backlog itself is a living artifact, reflecting not only the team’s capacity and technical possibilities but also the strategic vision and emergent insights from users. By maintaining a clear, prioritized backlog, the Product Owner ensures that the team’s efforts are consistently focused on the most impactful work, reducing waste and enhancing the probability of success.
Scrum’s iterative approach is reinforced through structured events, each serving a distinct purpose in promoting transparency, inspection, and adaptation. Sprint planning sets the stage for work by establishing a clear goal and identifying backlog items that contribute meaningfully to that goal. This planning process is inherently collaborative, requiring input from the entire team, and emphasizes the trade-offs between ambition and feasibility. Daily scrums, brief yet critical, allow the team to align efforts, surface obstacles, and adjust plans in real time. Sprint reviews provide an opportunity to demonstrate completed work to stakeholders, gather feedback, and recalibrate priorities. Finally, retrospectives create a dedicated space for reflection, allowing the team to identify areas for improvement and commit to actionable changes. Together, these events create a cadence of learning, communication, and continuous improvement that distinguishes Scrum from traditional approaches.
The Development Team is the engine of Scrum, and understanding how to leverage its full potential is essential. Teams are self-organizing and cross-functional, which means they possess the collective skill set necessary to deliver increments independently. This autonomy fosters creativity and accountability, as each member contributes not only to execution but also to decision-making about how work is approached. Within this framework, the role of the Product Owner is to provide clarity and context, ensuring that the team’s autonomy operates within a strategic framework. By balancing freedom with alignment, the Product Owner enables teams to innovate while remaining focused on outcomes that deliver value. For PSPO I aspirants, mastering this balance is essential, as it directly influences the effectiveness of backlog management and prioritization.
Empiricism is the bedrock of Scrum practice. The framework relies on evidence-based decision-making rather than prediction or assumption. Every artifact, event, and increment provides data that informs subsequent decisions. By observing outcomes, measuring progress, and adjusting plans accordingly, teams reduce risk and improve alignment with customer needs. For Product Owners, this principle manifests in continuous backlog refinement, reassessment of priorities, and responsive planning. Empirical thinking encourages flexibility and resilience, enabling teams to adapt to changing circumstances without losing sight of long-term goals. This mindset is critical for PSPO I preparation, as it underscores the importance of learning from results, not just completing tasks.
The focus on delivering increments of usable value is a defining characteristic of Scrum. By breaking work into small, testable units, teams create opportunities for frequent feedback and rapid learning. Each increment serves as a tangible demonstration of progress, allowing stakeholders to validate assumptions and influence future work. This approach contrasts sharply with traditional project management, which often delays feedback until a final product is complete, increasing the risk of misalignment with customer expectations. Incremental delivery ensures that value is realized early and continuously, reinforcing the connection between effort and impact. Product Owners play a pivotal role in this process by prioritizing backlog items that maximize early value and ensuring that each increment aligns with strategic objectives.
Scrum also emphasizes the human dimension of work, recognizing that the interactions between people are as important as the processes they follow. Psychological safety, open communication, and mutual respect are fundamental for fostering collaboration, innovation, and resilience. Teams that operate in an environment of trust can experiment, surface problems, and iterate rapidly without fear of blame or reprisal. The Product Owner contributes to this culture by providing clarity, guidance, and support, enabling team members to focus on creating value. By cultivating an environment that encourages participation and shared responsibility, Scrum ensures that organizational knowledge is leveraged effectively and collective intelligence is harnessed to solve complex problems.
Continuous improvement is embedded in every aspect of Scrum. Through retrospectives, feedback loops, and incremental learning, teams refine their processes, interactions, and outputs. The Scrum Master facilitates this growth by helping the team identify inefficiencies, experiment with solutions, and sustain progress over time. For Product Owners, this continuous improvement extends to the management of the backlog, stakeholder engagement, and value prioritization. By analyzing outcomes, incorporating lessons learned, and adjusting strategies accordingly, teams create a virtuous cycle of enhancement that strengthens both performance and product quality. PSPO I candidates must understand how to leverage this iterative learning to maximize the alignment between delivered work and strategic goals.
Risk management in Scrum is integrated seamlessly into its iterative, empirical approach. By delivering increments early and often, teams reduce the likelihood of large-scale failures and can address issues before they escalate. This proactive approach to risk is complemented by regular inspections and adaptive planning, which enable teams to respond to emerging challenges quickly. Product Owners must evaluate risk in terms of potential value lost or delayed, balancing short-term gains with long-term objectives. By integrating risk assessment into backlog prioritization, planning, and review, Scrum practitioners ensure that work progresses in a controlled, informed manner, optimizing both efficiency and impact.
Scrum’s versatility allows it to be applied across diverse industries, team structures, and product types. While often associated with software development, the framework’s principles are relevant wherever complex, adaptive challenges exist. Its emphasis on transparency, collaboration, empirical learning, and incremental delivery makes it suitable for marketing initiatives, product design, operational improvements, and strategic planning. For Product Owners, this universality requires the ability to contextualize Scrum practices to the specific environment, aligning artifacts, roles, and events with organizational objectives. PSPO I certification equips practitioners with the conceptual understanding and practical skills to apply Scrum effectively across varied contexts, ensuring that value is delivered consistently.
Scrum mastery requires a deep understanding of its principles, roles, and practices. Product Owners, particularly those pursuing PSPO I, must internalize the framework’s philosophy, embrace empirical thinking, and develop skills in value assessment, backlog management, and stakeholder engagement. By doing so, they can guide teams toward high-value delivery, foster continuous improvement, and navigate the complexities of adaptive work environments. Scrum is more than a method; it is a mindset, a disciplined approach to creating meaningful outcomes, and a system that empowers teams to realize their potential while delivering exceptional value. Mastery of Scrum transforms both the way work is approached and the results that are achieved, creating a sustainable, adaptive, and value-focused culture.
Scrum is not just a methodology; it is a mindset that transforms how work is approached, organized, and executed. Within this framework, the Product Owner holds a uniquely influential position, tasked with bridging the vision of the organization, the expectations of stakeholders, and the capabilities of the development team. For those preparing for PSPO I, understanding this multifaceted role is essential. The Product Owner operates at the intersection of strategy and execution, guiding decisions that determine both the trajectory of a product and the effectiveness of the team delivering it. Success in this role depends on mastering the delicate balance between delivering immediate value and maintaining alignment with long-term objectives, requiring acute analytical skills, empathy, and the capacity to adapt continuously.
Central to the Product Owner’s responsibility is the management of the product backlog, which serves as the living, breathing repository of all work items that can generate value for the organization. Effective backlog management goes beyond simple prioritization; it is a strategic exercise in forecasting impact, evaluating dependencies, and sequencing initiatives to maximize return. Items must be described with clarity, allowing the development team to understand the scope and purpose while leaving room for their creativity in solution design. A well-maintained backlog enables teams to operate with autonomy, reduces friction in sprint planning, and ensures that attention is consistently focused on initiatives with the highest potential value. Mastery of this aspect is a cornerstone of PSPO I proficiency.
Scrum encourages incremental delivery, a principle that shifts the focus from delivering large, monolithic solutions at the end of a project to producing small, usable increments continuously. Each increment becomes a learning opportunity, providing feedback from stakeholders, customers, and end-users. The Product Owner is responsible for translating this feedback into actionable backlog adjustments, maintaining alignment between delivered work and strategic priorities. This cycle of delivery, feedback, and adjustment transforms uncertainty into actionable insight, creating a system where risks are identified early, adaptations are made quickly, and the team’s efforts consistently contribute to meaningful outcomes. For PSPO I aspirants, understanding this iterative feedback loop is crucial for both examination readiness and real-world product success.
Collaboration within Scrum is paramount. The Product Owner must maintain clear, continuous communication with both the development team and external stakeholders. This communication is not merely transactional; it is relational, designed to foster trust, understanding, and alignment. Daily interactions provide opportunities to clarify expectations, resolve ambiguities, and preempt potential obstacles. By being accessible and responsive, the Product Owner ensures that the team can progress without unnecessary delays and that stakeholders are confident in the direction and pace of development. Such collaboration emphasizes the human-centric aspect of Scrum, reinforcing that the framework’s success depends as much on relationships as on processes.
Understanding value is a critical competency for the Product Owner. Value extends beyond financial metrics to include user satisfaction, market positioning, and strategic advantage. Each backlog item must be evaluated for its potential to deliver meaningful benefits, taking into account dependencies, risks, and resource constraints. Prioritization is thus both an art and a science, requiring judgment, intuition, and analytical rigor. Decisions about what to tackle first, what to defer, and what to de-prioritize have cascading effects on both the development team’s efficiency and the organization’s overall success. PSPO I certification emphasizes the Product Owner’s role in continuously assessing, re-assessing, and communicating these value-driven priorities.
The iterative nature of Scrum necessitates disciplined planning and adaptability. Sprint planning sessions are the mechanism through which the Product Owner collaborates with the development team to define achievable goals and align expectations. During planning, the Product Owner clarifies the intent behind each backlog item, explains its expected value, and negotiates scope within the constraints of the sprint. This interaction not only ensures shared understanding but also empowers the team to make informed decisions about execution. Adaptability is reinforced as priorities shift, new insights emerge, or unforeseen impediments arise. The Product Owner’s ability to respond effectively to these changes directly influences the team’s capacity to deliver consistently high-value increments.
Empirical thinking is another foundational principle underpinning effective Scrum practice. Decisions are informed by observation, measurement, and reflection rather than assumption or intuition alone. This empirical approach allows the Product Owner to refine both strategy and execution, using real outcomes to validate hypotheses and guide future actions. Performance metrics, user feedback, and stakeholder input all serve as inputs for evidence-based decision-making. Over time, this creates a feedback-rich environment where learning is continuous, risk is mitigated, and product evolution is guided by tangible insights rather than speculative plans. Mastery of this principle is critical for PSPO I candidates, equipping them to lead with confidence and precision.
The role of the Product Owner is also integrally tied to risk management. Scrum reduces risk inherently through short, iterative cycles, early delivery, and continuous feedback. However, the Product Owner must actively identify potential obstacles that could impede progress, whether they stem from technical constraints, changing market conditions, or misaligned expectations. By addressing these risks proactively—through backlog refinement, stakeholder engagement, or strategic re-prioritization—the Product Owner helps ensure the team maintains momentum and consistently delivers value. The ability to balance risk with opportunity is an advanced skill that distinguishes highly effective Scrum practitioners from those merely following the framework.
Psychological safety is a vital aspect of effective Scrum teams. A Product Owner who fosters an environment where team members feel secure in sharing ideas, challenging assumptions, and admitting mistakes promotes innovation and accelerates learning. This environment encourages the exploration of alternative approaches, experimentation, and creative problem-solving, all of which are necessary when dealing with complex, adaptive challenges. The Scrum Master and Product Owner must work in tandem to maintain this culture, combining support, guidance, and protection from unnecessary external pressures. PSPO I aspirants must recognize the importance of these cultural dynamics and their direct impact on value creation and team performance.
The integration of strategic vision with operational execution differentiates exceptional Product Owners. They not only understand what the organization seeks to achieve but also translate that vision into actionable initiatives that the team can implement. This requires a comprehensive grasp of both market dynamics and internal capabilities, ensuring that every increment produced contributes meaningfully toward long-term goals. Backlog items are not simply tasks to be completed; they are strategic vehicles for advancing organizational objectives. By consistently linking daily work to overarching outcomes, the Product Owner ensures that Scrum is not merely a process but a driver of sustainable competitive advantage.
Product discovery is another critical domain where Product Owners demonstrate impact. The process of identifying customer needs, validating assumptions, and testing hypotheses informs backlog prioritization and product strategy. By engaging with real users, analyzing data, and iterating based on empirical insights, the Product Owner ensures that the product evolves in a manner that maximizes value and minimizes wasted effort. Discovery is continuous, and its outcomes directly shape the backlog, influencing what the team works on next and how resources are allocated. PSPO I preparation emphasizes understanding this dynamic process, equipping practitioners to make informed decisions that consistently enhance product effectiveness.
Ultimately, Scrum mastery for Product Owners involves harmonizing multiple dimensions of work: strategic thinking, backlog management, iterative delivery, risk assessment, stakeholder engagement, and team dynamics. Each dimension interacts with the others, creating a complex yet coherent system that drives consistent value creation. For PSPO I aspirants, success requires more than theoretical knowledge; it demands the ability to apply principles in real-world scenarios, balancing competing demands, adapting to change, and leading teams toward meaningful outcomes. Through deliberate practice, reflection, and continuous learning, Product Owners can elevate both the performance of their teams and the impact of the products they steward.
Scrum is therefore a holistic framework that unites philosophy, strategy, and execution. The Product Owner sits at the nexus of this framework, accountable for aligning vision, guiding priorities, and enabling teams to deliver value iteratively. By embracing the principles of empiricism, transparency, collaboration, and continuous improvement, the Product Owner transforms uncertainty into opportunity, challenges into insights, and incremental work into high-impact outcomes. The pursuit of PSPO I certification formalizes this understanding, providing the knowledge and skills necessary to navigate the complexities of product ownership effectively. In doing so, Product Owners become not only facilitators of Scrum but also architects of value, innovation, and sustainable success.
Have any questions or issues ? Please dont hesitate to contact us