Your cart is empty
Add prompt packs to continue
This master collection of Scrum prompts has been designed to radically transform the efficiency of Scrum Masters, Product Owners and development teams. Through precise instructional engineering, this resource allows you to automate the creation of artifacts, optimize the facilitation of ceremonies and deepen the analysis of critical metrics, eliminating ambiguity in each phase of the agile framework. By integrating these prompts into their workflow, professionals will be able to scale their strategic capabilities, ensuring that every User Story meets the highest standards and that every Sprint Retrospective drives real change. It is the definitive tool for those seeking to lead an agile transformation based on data, tangible results and impeccable communication with all levels of the organization.
100 resources included
He acts as a Senior Agile Coach and Organizational Transformation Consultant with specialization in empirical frameworks and high performance culture. Your mission is to execute a deep and multidimensional "Agile Health Audit" for the [Team or Project Name] team, which operates within the [Industry/Sector] sector and currently has an agile maturity level qualified as [Maturity Level: Initial/Intermediate/Advanced]. The main objective is to break down the effectiveness of your Scrum implementation and detect if the agility is genuine or if the team is stuck in an "Agile In Name Only" (AINO) model. To carry out this diagnosis, analyze in detail the interaction between the fundamental roles: the Product Owner, the Scrum Master and the Development Team. Evaluate how they manage the [Specific Artifact: Product Backlog/Sprint Backlog/Increment] and whether the Scrum events (Planning, Daily, Review and Retrospective) are fulfilling their purpose of inspection and adaptation or if they have become worthless bureaucratic meetings. You must consider contextual factors such as the pressure for fixed delivery dates, the real autonomy of the team to self-manage, and the technical quality of the product generated in each iteration under the definition of done (DoD) used by [Company Name]. Incorporate into your analysis critical flow metrics such as [Metric 1: e.g., Cycle Time], [Metric 2: e.g., Throughput], and the level of [Culture Variable: e.g., Psychological Safety] that you perceive in the environment. Identify bottlenecks in external communication with stakeholders and evaluate whether the value flow is interrupted by unresolved organizational dependencies. It is vital that the diagnosis is not only operational, but rather penetrates the cultural layer, analyzing whether there is a growth mentality or whether the fear of error is holding back the innovation and experimentation necessary in complex environments. The final result of this audit should be a structured executive report that contains: 1. An Agile Health Radar (assessment from 1 to 5 on key dimensions), 2. A SWOT analysis focused exclusively on the team's agility, 3. A list of 'Anti-patterns' detected with their respective root causes, and 4. A [Term Time: e.g., 3 months] Transformation Roadmap with concrete actions, suggested owners and success KPIs to evolve towards. a state of high performance and continuous value delivery.
He acts as a Senior Product Owner and Corporate Communication Strategist with 15 years of experience in agile environments and key account management. Your primary objective is to write a high-impact report titled 'Communication of Delivered Value' designed specifically for [Stakeholder Profile: Ex. Management Committee, External Clients, Investors]. This document should transcend the simple enumeration of technical tasks completed in Jira and focus exclusively on the strategic impact, risk mitigation and return on investment (ROI) generated during the period of [Time Period: Ex. Sprint 15, Q3, Month of July]. To build this report, use the following base information that I provide you: 1. Strategic Objectives of the Cycle: [Describe what business goals were sought to be achieved]. 2. Key Product Increments: [List the functionalities or improvements delivered]. 3. Quantifiable Impact Metrics: [Ex. Reduction in error rate by X%, improvement in user conversion by Y%, or savings of Z man hours]. 4. Qualitative Feedback: [Cite comments from end users or market validations]. 5. Obstacles Overcome: [Briefly mention technical or business challenges resolved]. Required Output Structure: 1. Executive Value Summary (The 'Bottom Line'): A powerful paragraph that explains the direct benefit to the business immediately. 2. Value Matrix vs. Effort: An explanation of how the delivered functionality optimizes current resources. 3. Impact on Business KPIs: Direct correlation between the work of the Scrum team and the organization's success indicators. 4. Future Vision and Roadmap: A brief section on how this value delivered paves the way for the next milestones [Mention Upcoming Milestones]. 5. Expectation Management: If there were backlog items that were not delivered, explain it under a narrative of prioritizing value and quality over quantity. Style and Tone Guidelines: Language should be [Tone: Ex. Executive, Persuasive, and Evidence-Based]. It is imperative that you translate technical concepts (e.g. database refactoring) into business benefits (e.g. scalability and reduced maintenance costs). The report should be concise, visually structured (using bullets and bold), and ready to be emailed or presented at a stakeholder review meeting.
Acts as a Senior Product Owner expert in executive communication and strategic project management under the Scrum framework. Your objective is to write a comprehensive and professional 'Roadmap Progress Report' for the external stakeholders of the [Project Name] project for the period [Report Period]. The report should balance technical transparency with a strategic business vision, ensuring that stakeholders understand the value delivered to date and the path forward without overwhelming them with unnecessary technicalities. It begins with a high-level executive summary that defines the overall health status of the project (Healthy, Under Watch, At Risk) and summarizes the three most significant achievements achieved during this cycle. Use a professional, direct and results-oriented tone. It is essential that this first paragraph provides management with the necessary confidence about the direction of the product and the efficiency of the Scrum team in delivering incremental value. Breaks down the current status of the key milestones defined in the original roadmap using the data provided in [Key Milestones Status]. For each milestone, indicate the percentage of completion, the estimated delivery date, and a brief description of the impact this functionality will have on the organization's KPIs. If there have been chronological deviations, explain the root causes (technical blockages, changes in market priorities or external dependencies) and briefly describe the corrective actions that have been implemented to maintain strategic alignment. It incorporates a performance analysis section based on [Speed/Burnup Metrics]. Translate these agile metrics into business language, explaining how the team's current capacity enables (or limits) future scope expansion. Logically justify any adjustments to priorities under the [Changes in Scope] section, linking them directly to feedback received from end users or changes in the company's competitive environment. End the report with proactive risk management based on [Current Risks]. Identify critical factors that could impact the schedule in the next quarter and detail corresponding mitigation plans. Conclude with a 'Next Steps and Required Decisions' section based on [Next Steps], explicitly requesting stakeholder support or validation at key points to avoid project governance bottlenecks.