Paweł Kalkus’ Post

Professional Scrum Product Owner Advanced (II) - Summer edition (8 - 9.08) 25% cheaper than the standard price! Where and when: online, 9:00 - 17:00, 8 - 9.08.2024 Language: english Two exam attempts (PSPO II) included in the price. If you're interested in learning new skills as a Product Owner and upgrading your position on the job market, this training is for you! As part of the training you will: - Find out what to do and what NOT to do as a Product Owner in a Scrum Team - What traps and dysfunctions you should avoid in order to enable to team to deliver value regularly - How to measure value from the customer and organizations perspective - How to delegate product backlog management activities so that you have more space to consider the big picture - How to follow the market trends, experiment with pricing strategies and come up with innovative product solutions - What to consider when scaling up product development - How to manage stakeholder's needs and requests and maintain a healthy relationship with them If you're interested, let me know in a private message by the end of the day and you'll get a 25% discount as well as a number of additional bonuses: - one on one consultations, - video trainings about Scrum and Agile, - a dedicated 1 hour session for the entire group to prepare for the PSPO II exam as well as a mock test that will help you get a better understanding of what's expected.

🚀 Ever wondered how to make your Daily Scrums as effective as possible? Boost the full potential of your Scrum team with my Scrum Master course! Here’s how this course will transform your approach and increase productivity: 🔍 Master Progress Tracking: Learn to effectively inspect progress towards your Sprint Goal, adapt your Sprint Backlog, and keep your team focused on what matters most. ⏱ Achieve Meeting Efficiency: Discover proven techniques to conduct 15-minute stand-ups that are concise and impactful, ensuring your meetings are productive and to the point. 🗣 Empower Developer Self-Management: Equip developers with the skills to lead their own updates, address blockers promptly, and create actionable plans for the day, fostering greater ownership and efficiency. 🛠 Optimise the Scrum Master’s Role: Find out how Scrum Masters can support their teams without taking over, facilitating effective stand-ups while letting the team take the lead. 🔄 Adapt and Overcome Challenges: Get practical tips for managing blockers and keeping discussions focused. Learn how to handle detailed issues outside the stand-up to maintain meeting effectiveness. 🔄 Flexible and Practical Insights: Explore how the Daily Scrum fits into your Agile process and discover strategies to integrate these practices seamlessly, enhancing overall workflow and team collaboration. Ready to elevate your Scrum practice and make every Daily Scrum count? Enrol in my course today and drive your team’s success! https://2ly.link/1zDvF ⏯ Follow Michael James on YouTube for free content https://2ly.link/1zDvb @LearnManagementOnline  or on any other platform (LinkedIn, Facebook, Insta, Tiktok)  Here are my social links https://2ly.link/1zDve 💡Or buy direct from me for the Udemy discount value: https://2ly.link/1zDvm Further bundle discounts here https://2ly.link/1zDvl #Scrum #Agile #DailyScrum #ScrumMaster #DeveloperSuccess #Course #ProfessionalScrumMaster #MichealJames #Transformation #LearnManagementOnline

When scrum.org thought about what a professional Product Owner should do to succeed, it identified three key concepts - vision, value, and validation. ✔️Vision: The most crucial step a Product Owner can take to truly take responsibility and inspire others is to create and communicate a clear vision for the product. Why are we creating this product? Whose lives will it benefit? ✔️Value: To shift from project thinking (time, budget, scope) to product thinking (value for stakeholders), a Product Owner must define and communicate what product success looks like. Is success measured by increased customer satisfaction? Reduced operational costs? Increased user registrations? How will we measure it? How will we understand if the value achieved outweighs the costs? ✔️Validation: The best way for a Product Owner to actively manage risks is by shortening the feedback loop through frequent checks, at least with internal experts, and ideally with the external market. A professional product owner understands that the only way to move the needle on any value metric is to release the product to the market. Until then, it's all just a hypothesis. A professional product owner embraces empiricism as a method to reduce the complexity and risk of creating something unknown. The three key concepts perfectly align with the three pillars of empiricism:  🔜Vision: creates transparency.  🔜Value: defines what needs to be inspected.  🔜Validation: leads to adaptation. ⚡️We talk more about product development in our Professional Scrum Product Owner training. Join us!

Scrum Product Owner Training The free online course describes how to manage a product backlog and engage with stakeholders to ensure deliverables. The Scrum Product Owner Certified (SPOC) course teaches product managers how to manage and maximize the value of product backlog. You will discover how to work in an Agile environment and we will focus on the product requirements to manage the product outcome. This course prepares you to use tools that help product managers to translate requirements to the development team to achieve the optimum results in their business. #freecourse #freelearning #alison #Alison #Scrum #Product #Owner #Training #business #businesscourse

Unlocking Value with Scrum: A Quick Guide for Busy Leaders To deliver product value efficiently is more critical than ever. And “products” doesn’t just mean software! Whether you’re developing a new marketing campaign, streamlining internal processes, or launching a physical product, Stakeholders, Product Owners, Project Managers, and CEOs all share the same goal: Achieving maximum impact with minimal waste. How do you ensure your teams are working effectively with efficient product delivery and adapting quickly to change? Enter Scrum, a proven framework for agile product development (and beyond!) It is a structured yet flexible approach that empowers teams to deliver incremental value frequently and predictably, no matter what they’re building. What is Scrum? Imagine a team of experts working collaboratively in short, focused cycles (called Sprints.) They prioritize the most valuable features, build them, gather feedback, and adapt their plan accordingly. This iterative process ensures continuous improvement and alignment with your strategic goals. Why Should Leaders Care About Scrum? Stakeholders: See tangible progress and provide feedback early and often, ensuring the product continuously meets your needs. Product Owners: Gain a clear framework for managing the product backlog and maximizing the value delivered to customers. Project Managers: Benefit from increased transparency, efficient collaboration, and ongoing risk management. CEOs: Drive innovation and achieve a competitive edge while fostering a culture of agility and customer-centricity. Understand and Empirically Measure Your Agile Journey with Our Scrum eBooks To assist with your understanding and the efficient implementation of Scrum, we offer two comprehensive eBooks: https://lnkd.in/dFFmaZfx

💡 Is Scrum Really Agile? Some argue that Scrum doesn’t fully align with Agile. While Scrum is a framework, it’s still flexible and adaptive, making it a great fit for many teams and can help to actualize Agile. 📜 It’s important to remember that Scrum’s creators—Ken Schwaber, Jeff Sutherland, and early adopter (and my mentor) Mike Beedle—were signatories of the Agile Manifesto. Scrum actually existed before the Agile Manifesto, and the creation and practices of Scrum impacted the values and principles found in the Manifesto. 📊 We’re looking at how the 2020 Scrum Guide aligns with the Agile Manifesto values and principles (check the attached image for a detailed breakdown). The guide outlines the minimum required to call it Scrum. But if Agile is what we aspire to, we can use Scrum in a way that maximizes this alignment—what I call Bright Scrum. On the flip side, when there’s low alignment, it can turn into what Ron Jeffries calls Dark Scrum. Here’s the alignment breakdown of some of the values and princples 🧵: ✅ Strong alignment: Delivering working software Responding to change Enabling self-managing teams 🟡 Medium alignment: Customer collaboration 🔴 Low alignment (some inferences to alignment though): Simplicity (Scrum implies simplicity, but it’s not explicitly emphasized) Business and developers working together daily (Product Owner often bridges this but not explicit) Face-to-face communication Scrum thrives on transparency, inspection, and adaptation. You can go beyond the minimum outlined in the Scrum Guide and aspire to Bright Scrum, aligning more deeply with Agile’s core principles. But, out of the box Scrum aligns pretty well, but, not perfectly. Check out my full article in the comments with a detailed table mapping and ranking of each value and principle to Scrum. Note: this is not about liking or not liking Scrum or saying it is the right approach. Just how it aligns and does not align with Agile. #agile #scrum #brightscrum #selforganizingteams #agilemanifesto

Upskilling for Agile Success: Are you ready to truly commit? 📚 Upskilling yourself and your team before implementing agile should be your top priority. But who should learn what? Agile isn’t just about tools and processes; it's about mindset and team culture. Thus, start with an interactive agile mindset training to experience the fundamentals needed for success. This is often overlooked, but it lays the essential foundation. 💡Agile Mindset: Focus on interactive workshops to challenge and grow your agile mindset. Then have framework-specific trainings follow. Let’s assume you are implementing Scrum… 📘 Agile Basics Training: Learn the fundamental principles and practices of Scrum. Followed by... 📌 Role-Specific Trainings: 👨🏫 Scrum Masters: Learn coaching, training, and meeting facilitation. 📊 Product Owners: Focus on agile requirements and stakeholder management. 👥 Developers: Understand your responsibility as a self-managed team member. 🧩 Stakeholders: Experience how to best empower and support the agile team and become aware of the impact your behaviour has. 🎓 Certifications: Optional but beneficial. PSM & PSPO I certifications from Scrum.org can prove your understanding. Use ChatGPT and online quizzes for preparation. But remember, certifications alone don’t make you agile. Ready to transform your team with agile? Let's connect and get you started! 💬

✨"Day20/100 of Agile & Scrum Learning: Join Me for a Daily Dose of Insight!"✨ 💥**User Stories**💥 User stories are short, simple descriptions of a feature or requirement from the perspective of the end user. They help teams understand what the user needs and why it’s important. The typical format is: As a [type of user] I want [some goal] so that [some reason] 💡Best Practices for Writing User Stories 📍Keep It Simple: Use clear, straightforward language. Avoid jargon. 📍Focus on User Needs: Center the story around what the user wants to achieve, not just the feature itself. 📍Add Acceptance Criteria: Define clear conditions that determine when the story is complete. 📍Make It Testable: Ensure the story can be verified against the acceptance criteria. 📍Prioritize: Rank user stories based on their importance to the user and the project. 📍Collaborate: Involve users and stakeholders in the writing process to capture their needs accurately. 📍Use INVEST Criteria: ⚙Independent: Can be developed separately. ⚙Negotiable: Flexible; not a contract. ⚙Valuable: Delivers value to users. ⚙Estimable: Can be estimated for effort. ⚙Small: Small enough for one iteration. ⚙Testable: Can be verified. 📍Vertically Sliced: User story includes all necessary components (frontend, backend, database, etc.) needed to implement a specific user function. 💡 Who writes User stories: User stories can be written by various stakeholders, but they are typically authored by: 🔍 Product Owners: In agile teams, the product owner is often responsible for writing user stories, as they have a deep understanding of user needs and the product vision. 🔍Business Analysts: They may also write user stories, especially in larger teams, as they bridge the gap between stakeholders and the development team. 🔍Developers: In some cases, developers might write user stories based on their understanding of user needs and requirements. 🔍Users/Stakeholders: End users or other stakeholders can contribute to writing user stories, ensuring that their needs and perspectives are accurately captured. 🔍Collaborative Workshops: Teams often hold meetings where multiple stakeholders collaborate to brainstorm and write user stories together. This ensures a shared understanding of the requirements. #agile #scrum #scrummaster #100daysofagile #100daysoflearning #usertsories

Day 26 of My 30-Day Scrum Learning Challenge 10Alytics Today, I learned about scaled Scrum and how it enables agile practices across more prominent organizations. Here's what I've learned: What is scaled Scrum? Scaled Scrum is an approach whereby Scrum practices are implemented across multiple teams working on the same product. This becomes quite important in large organizations where one Scrum team cannot handle all aspects of a project. This will ensure that Scrum principles are upheld while coordinating efforts across different teams. SAFe (Scaled Agile Framework) provides a structured approach for scaling agile practices, including roles, responsibilities, and events, across multiple organizational levels. Why Scaled Scrum is Important: Consistency: Maintains consistent Scrum practices across multiple teams, ensuring alignment and cohesion. Coordination: Facilitates better coordination and communication among teams working on different parts of the same product. Efficiency: Increases efficiency by leveraging shared practices and tools, reducing duplication of effort. Scalability: Enables organizations to scale their agile practices effectively as they grow and tackle larger projects. Implementing Scaled Scrum: Align Teams: Ensure all teams understand and adhere to common Scrum principles and practices. Establish Clear Roles: Define roles and responsibilities at the team and program level to ensure clarity and accountability. Synchronize Events: Coordinate key Scrum events (e.g., Sprint Planning, Sprint Review) across teams to maintain alignment and transparency. Use Shared Backlogs: Maintain a single Product Backlog or a well-coordinated set of backlogs to ensure all teams work towards common goals. Continuous Integration: Implement continuous integration practices to merge code changes from all teams regularly, reducing integration challenges and ensuring a cohesive product. Benefits of Scaled Scrum: Improved Collaboration: Enhances collaboration and team communication, leading to better decision-making and problem-solving. Greater Flexibility: Allows organizations to adapt to changes quickly, even when dealing with large and complex projects. Enhanced Quality: Ensures high-quality product delivery through continuous integration and collective ownership. Faster Delivery: Accelerates the delivery of valuable products to customers by leveraging the collective effort of multiple teams. Understanding Scaled Scrum has been eye-opening, revealing how agile principles can be effectively applied at scale to drive organizational success. I am excited to see how these practices can be implemented to enhance our agile journey! 10Alytics Jabir Muhammad Ibrahim #Scrum #Agile #ProjectManagement #LearningJourney #30DayChallenge #10Alytics

My Scrum is real Scrum. My Agile is true Agile. After spending more than a decade in Agile and Scrum teaching/coaching and consulting, I understood the following and wanted to share it before officially hanging my boot next year. 1st—We don't need agile communities anymore. Participation has decreased in these community events. Ample knowledge is available, so people want to hear your experiences and not theory and solve their problems, which is impossible. You can get clues from someone's experience but can't copy-paste. It is better to focus on building communities within the organization with a wider scope and not limited to scrum masters or agile coaches. 2nd—Comparing certification bodies is a useless effort. Nobody can tell you better than me because I am associated with all popular agile and scrum certification bodies. If I am not associated with them, they are not worth considering. Even Scrum or Kanban is good to start with and establish your process over some time. 3rd—Your company never intended to be agile, or you lack the capabilities to coach your organization. None of these is bad. The goal for the company is to be innovative and not become the slave of any agile framework. Everyone doesn't become a coach, even if you are the best player, so it is okay. Organizations should consider simplifying funding, governance, procurement, and other parts of their operations rather than building multiple squads and tribes. 4th—If you think you are the best and your framework is better than others, you are outdated. Always believe that the best is yet to come, and a framework has to emerge. Learn and share, but demonstrate openness and appreciate the feedback. I can talk and share more if you offer a good coffee 😊 Preeth Sumeet Piyush Satyajit Atulya Agilemania Ashwinee #agile #scrum #agilemania