Amina E.

In an Agile environment, you need to be an adaptable, proactive self-starter. Most of the other scrum team members won’t habitually think of reaching out to the documentation team to notify you that a new feature or enhancement has a documentation impact. If you are new to the Agile process, keep in mind that adopting Agile is itself a significant change process. For technical writers, being Agile is more about relationship-building than anything else. It can take some time for an organisation to fully embrace the Agile mindset, and in engineering-driven scrums, engineers and program managers often don’t include documentation in the definition of done because it’s too difficult to track docs as an outlying activity. You have to evaluate the kind of scrum team you’re on, as well as the specific information you have to develop, before you can decide on what approach you’ll take to Agile and how closely to tie your work to the software development.

1

Most teams confuse commissioning with assurance. They're not the same. Commissioning checks if systems start. Assurance ensures they endure. Independent Verification & Validation (IV&V) complements—not duplicates—commissioning. It pressure-tests systems against edge conditions, not just vendor handoffs. It's not about catching flaws after go-live. It's about de-risking before Day One. The best in the business don’t wait for failure to simulate stress. They build for it. Their commissioning playbooks test like they deploy: under pressure, at scale, with real-world variables. Simulation isn’t theory—it’s a risk-reduction asset. And IV&V is the neutral lens that proves resilience before the market, regulators, or headlines do. At CIO Eureka Consortium, our IV&V teams bring a battle-tested mix of engineering rigor and operational realism. We’ve helped agencies, hyperscalers, and Fortune 100s translate plans into performance—with fewer surprises and tighter outcomes. Assure before you launch. Trust, but simulate. @Asociación Mexicana de Data Centers MEXDC #IVandV #DataCenters #DigitalInfrastructure #BoardroomReadiness #LeadershipMatters #TheUncomfortableCEO

4

Reminder to all and note for those new to agile and scrum: A Product Owner is not a spec writer. Acceptance criteria define testable behavior -> not tasks. If your team says: “we need everything defined before we start” “refinement isn’t where decisions happen” “unclear = PO fault” Then you DO NOT have Scrum. You have spec-driven delivery hiding behind Agile. In other words, performance theater. #agile #productmanagement #SAFe

1

Definition of Done at Scale 🚀 Definition of Done is your quality contract, not a checklist. ✅ In one team, a weak DoD creates confusion. At scale, it creates rework, handoff gaps, integration pain, and late defects ⚠️ I’ve seen features marked “done” on one board… only to fail when another team touched them. That’s not done. That’s delayed discovery. When multiple teams work on the same product, DoD must become a shared quality agreement 🤝 Not bloated. Not bureaucratic. Just clear enough to protect flow and quality. A practical rule: Add one DoD item that prevents rework 🔁 That one rule can save more time than many status meetings. Because at scale, “done” should mean more than code complete. It should mean ready for the system, ready for the next team, and ready for real use 🎯 What Definition of Done item has saved you the most defects?

6

*Sunday Prompt* for you to use Here's a prompt I used this week on ChatGPT with a Scrum Master who was just beginning to research possibilities for his next role. If it's useful to you with whatever LLM you use, whether ChatGPT or Perplexity.ai or Gemini or other, just change some of the words to fit you and your next goal - and see what the results are. 𝘞𝘩𝘰 𝘣𝘺 𝘵𝘪𝘵𝘭𝘦 𝘩𝘪𝘳𝘦𝘴 𝘴𝘤𝘳𝘶𝘮 𝘮𝘢𝘴𝘵𝘦𝘳𝘴 𝘸𝘪𝘵𝘩 [𝘹] 𝘺𝘦𝘢𝘳𝘴 𝘦𝘹𝘱𝘦𝘳𝘪𝘦𝘯𝘤𝘦? 𝘞𝘩𝘢𝘵 𝘢𝘳𝘦 𝘵𝘩𝘦𝘴𝘦 𝘩𝘪𝘳𝘪𝘯𝘨 𝘮𝘢𝘯𝘢𝘨𝘦𝘳𝘴’ 𝘤𝘰𝘯𝘤𝘦𝘳𝘯𝘴 𝘢𝘯𝘥 𝘱𝘳𝘰𝘣𝘭𝘦𝘮𝘴 𝘵𝘰 𝘴𝘰𝘭𝘷𝘦? 𝘞𝘩𝘦𝘯 𝘵𝘩𝘦𝘺 𝘩𝘪𝘳𝘦, 𝘸𝘩𝘢𝘵 𝘥𝘰 𝘵𝘩𝘦𝘺 𝘴𝘢𝘺 𝘵𝘩𝘦𝘺 𝘸𝘦𝘳𝘦 𝘭𝘰𝘰𝘬𝘪𝘯𝘨 𝘧𝘰𝘳 𝘵𝘩𝘢𝘵 𝘸𝘰𝘳𝘬𝘦𝘥 𝘧𝘰𝘳 𝘵𝘩𝘦 𝘸𝘪𝘯𝘯𝘪𝘯𝘨 𝘤𝘢𝘯𝘥𝘪𝘥𝘢𝘵𝘦? 𝘞𝘩𝘢𝘵 𝘤𝘰𝘮𝘱𝘢𝘯𝘪𝘦𝘴 𝘪𝘯 𝘵𝘩𝘦 [𝘤𝘢𝘯𝘥𝘪𝘥𝘢𝘵𝘦’𝘴 𝘨𝘦𝘰𝘨𝘳𝘢𝘱𝘩𝘪𝘤] 𝘢𝘳𝘦𝘢 𝘩𝘪𝘳𝘦 𝘴𝘤𝘳𝘶𝘮 𝘮𝘢𝘴𝘵𝘦𝘳𝘴? 𝘸𝘩𝘢𝘵 𝘪𝘴 𝘵𝘩𝘦 𝘵𝘺𝘱𝘪𝘤𝘢𝘭 𝘱𝘢𝘺? 𝘈𝘳𝘦 𝘵𝘩𝘦𝘳𝘦 𝘪𝘯-𝘱𝘦𝘳𝘴𝘰𝘯 𝘰𝘳 𝘓𝘪𝘯𝘬𝘦𝘥𝘐𝘯 𝘰𝘳 𝘰𝘯𝘭𝘪𝘯𝘦 𝘯𝘦𝘵𝘸𝘰𝘳𝘬𝘪𝘯𝘨 𝘨𝘳𝘰𝘶𝘱𝘴 𝘧𝘰𝘳 𝘴𝘤𝘳𝘶𝘮 𝘮𝘢𝘴𝘵𝘦𝘳𝘴? 𝘓𝘰𝘤𝘢𝘭 𝘯𝘦𝘵𝘸𝘰𝘳𝘬𝘪𝘯𝘨 𝘨𝘳𝘰𝘶𝘱𝘴 𝘰𝘳 𝘓𝘪𝘯𝘬𝘦𝘥𝘐𝘯 𝘨𝘳𝘰𝘶𝘱𝘴 𝘧𝘰𝘳 𝘉𝘭𝘢𝘤𝘬 𝘐𝘛 𝘱𝘳𝘰𝘧𝘦𝘴𝘴𝘪𝘰𝘯𝘢𝘭𝘴? I added a couple of more comments, submitted it, and in 27 seconds got back 3 pages of helpful research results for this candidate. The candidate had already done their resume using ChatGPT which I could tell because he used similar phrasing to everyone else using an LLM to "do" their resume! So in a new service I have, I went through the resume with the candidate, refreshing some of the language to make it more individual and a better match for current scrum master openings - and thus way more likely to get the attention of hiring managers 𝘢𝘵 𝘤𝘰𝘮𝘱𝘢𝘯𝘪𝘦𝘴 𝘩𝘦'𝘴 𝘵𝘢𝘳𝘨𝘦𝘵𝘪𝘯𝘨. His next prompt would likely be a request for open scrum master jobs in his geographic area, and of course as a key part of his strategy, he'd do networking and be more visible among his colleagues, in person and on LinkedIn. See this space next Sunday for another prompt that might be useful to you. Comments welcome!

8

Agile project management is a dynamic approach to leading projects that emphasizes adaptability, collaboration, and iterative development. As an experienced Agile Project Manager, I have found that effective leadership is crucial to the success of Agile teams. In this article, we will explore the key principles of Agile leadership, as well as the popular Scrum framework and other project management methodologies that can be integrated with Agile practices. One of the fundamental components of Agile leadership is creating a culture of trust, transparency, and empowerment within the team. This involves fostering open communication, encouraging self-organization, and supporting team members in making decisions autonomously. By empowering team members to take ownership of their work and providing them with the resources and guidance they need to succeed, Agile leaders can create a collaborative and innovative environment where individuals are motivated to deliver high-quality results. In addition to building a strong team culture, Agile leaders must also be able to adapt quickly to changing circumstances and priorities. This requires a flexible and responsive mindset, as well as the ability to effectively manage risk and uncertainty. By embracing change and continuously refining their approach based on feedback and lessons learned, Agile leaders can position their teams for success in complex and unpredictable environments. One of the most widely used frameworks within Agile project management is Scrum, which is based on an iterative and incremental approach to product development. Scrum is organized around short, time-boxed iterations known as sprints, during which cross-functional teams collaborate to deliver a potentially shippable product increment. The Scrum framework includes roles such as the Scrum Master, who is responsible for facilitating the Scrum process, and the Product Owner, who represents the stakeholders and prioritizes the backlog. By following the principles of Scrum, teams can improve communication, increase transparency, and deliver value to customers more efficiently. While Scrum is a popular choice for many Agile teams, there are other project management frameworks that can also be integrated with Agile practices, such as Kanban, Lean, and Extreme Programming

1

1 Comment

Most teams say they use Scrum, but the real key to success is the Definition of Done (DoD). The DoD isn't a checklist; it’s the most critical tool for building trust and enabling real team learning. If your DoD isn't clear, you’re just delivering Code Complete" and collecting messy code (technical debt). This makes your work unpredictable. Your Action Step: Stop relying on special "clean-up" Sprints later. Your DoD must include all quality steps now: security checks, full testing, and deployment to a staging environment. A strong DoD doesn't slow you down; it makes your releases safe and your work pace reliable. #Agile #Scrum #ProductDevelopment #ScrumMaster What's one thing you recently added to your DoD that improved your team's quality?

6

1 Comment

Struggling with Story Points (3, 5, 8)? The One Fixed Baseline Rule. 🛑 Click to view the full guide! 👇 #storypoints #agile #scrummaster #AgileCoach #productmanagement #pmi #pmp #pmpprep #pmpexam #PMPforPM #projectmanager #projectmanagement

7

Release Notes for "First Principles in Scrum: Implementing Scrum and Agile Practices" - July 10, 2025 Update https://lnkd.in/eASMHWPg We're excited to announce today's update to *First Principles in Scrum: Implementing Scrum and Agile Practices* (Volume 2 of the trilogy). As part of our ongoing commitment to evolving this book through iterative sprints—just like Scrum itself—we've added a brand-new chapter that bridges cutting-edge AI integration with the foundational principles of Scrum. What's New in This Update: - **New Chapter: "The Sutherland Doctrine: An Analysis of Scrum Sage and the Integration of First Principles into AI-Driven Agile Management"** - This comprehensive analysis explores Scrum Sage: Zen Edition Version 2, an AI-powered tool developed in collaboration with Dr. Jeff Sutherland. It positions Scrum Sage as the embodiment of Sutherland's "doctrine" for hyperproductive teams, synthesizing Agile mechanics, AI-driven predictive control, and first principles from fields like thermodynamics, neuroscience (e.g., Karl Friston's Free Energy Principle), computational physics (e.g., Stephen Wolfram's Computational Irreducibility), Lean manufacturing, and Zen philosophy. - Key highlights include: - A paradigm shift from reactive empirical process control to proactive, empirically-guided predictive control. - Detailed functional architecture of Scrum Sage, including AI features for backlog refinement, daily standups, retrospectives, and risk mitigation. - The "Zen Edition" philosophy for sustainable high performance, drawing on mindfulness and flow. - Scientific deconstruction of Scrum's foundations, with practical mappings to waste elimination and team dynamics. - Recommendations for adopting Scrum Sage in mature Agile organizations. - This chapter (spanning Sections 1–5, with tables, examples, and a full works cited) demonstrates how AI can augment—not replace—human Scrum Masters, fostering symbiosis for better decision-making and reduced cognitive load. #### Why This Matters: This addition embodies the book's Scrum-based creation process: we "sprint" new content to address emerging trends, like AI's role in Agile. It builds on Volume 1's foundations and sets the stage for Volume 3's advanced strategies. If you're exploring how first principles can supercharge AI tools in your teams, this chapter is a must-read—it's not just theory; it's actionable insight for achieving hyperproductivity. As always, this book is a living document. Future sprints will bring more chapters and refinements. If you have feedback or suggestions, reach out via Leanpub or the Scrum community. Thank you for your continued support. Let's keep accelerating together! Best regards, Jeff Sutherland, Ph.D. (and the AI collaborators: Grok 4, Gemini 2.5 Pro, GPT-o4, Claude 3.5, and others)

100

11 Comments