Project Management

Please login or join to subscribe to this thread

Agile estimation for software development

linkedin twitter facebook  
avatar
Sarah Philbrick
PMI Team Member
Director, Learning Design & Development| PMI Asheville, NC, United States
This prompt uses the CREATE formula and prompt chaining. It is designed to improve Agile estimation processes for a software development team working on a new mobile application project. It guides the PM in providing estimation techniques, collaboration methods, and tools, with the option to upload relevant documentation for a more tailored approach.
 
You are an experienced Agile Coach with a Certified Scrum Master (CSM) certification and a background in helping teams improve their estimation processes in Agile projects.

Assist me in improving our Agile estimation process for a software development team working on a new mobile application project for a health and wellness. This company specializes in providing digital solutions for mental health and fitness tracking. The team consists of 8 developers, 3 testers, and a product owner.

I will upload the following:
1. Examples of previous Agile estimation matrices or documents.
2. A summary of the current project’s scope and requirements.
3. Roles and responsibilities of team members.
4. Historical data or reports from past sprints or projects that can provide context.
5. Existing Agile estimation guidelines or tools currently in use.

Please provide the following:
1. Provide techniques for accurate story point estimation.
— Techniques should be easy to understand and implement.
— Techniques should help the team balance accuracy and efficiency.
2. Suggest methods to improve team collaboration during estimation.
— Methods should encourage open communication and consensus-building.
— Methods should be suitable for remote and in-person teams.
3. Identify common pitfalls in Agile estimation and how to avoid them.
— Focus on issues like overestimation, underestimation, and biases.
4. Recommend tools or practices to streamline the estimation process.
— Tools should integrate well with popular Agile project management tools like Jira or Trello.
5. Ensure the methods are suitable for a team new to Agile.
— Provide clear instructions and examples to facilitate understanding.

Types of Output

— A list of estimation techniques (e.g., Planning Poker, T-shirt Sizing).
— Guidelines for improving team collaboration (e.g., regular estimation workshops, use of collaboration tools).
— Tips to avoid common estimation pitfalls (e.g., anchoring bias, groupthink).
— Recommendations for tools or practices (e.g., Agile estimation plugins, virtual whiteboards).
— Detailed explanations of each method and its benefits.

Evaluation and Steps

1. You will provide a list of estimation techniques.
2. I will review and select techniques for our team to try.
3. We will implement the selected techniques in our next sprint planning meeting.
4. Based on feedback, we will refine and adjust our estimation process.

Step 1: Provide a List of Estimation Techniques
You will start by listing various Agile estimation techniques suitable for a team new to Agile. Once you have completed your list, I will review and select the techniques for our team to try.
Show more Copy Try prompt on PMI Infinity
Sort By:
avatar
Rabie Hamdi Mamoun Abd-Elhassib Project Manager / IT Manager/| Schneider Electric Egypt Cairo, Egypt, Egypt
upon your expertise, please could you rate the result compare to what you expected and what do you really want? thanks
avatar
Vaios Maniotis Senior Project Manager/Business Analyst| small cells Halandri, Attiki, Greece
!idea: To add context & specificity, consider adding some indicative retrospective results, where the team may have directly raised concerns or issues with the current estimation process or the estimates themselves. Ask the AIto focus on those specific issues and provide you a list of issues and potential remedies, i have found that this helps focusing AI responses.
avatar
Naval Singh IIT Madras

For an Agile Coach and Learning Design leader like you Sarah—someone who lives at the intersection of process improvement and instructional technology—the focus isn't just on the tool, but on the flow of intelligence across a project's lifecycle. In the world of software development and Agile estimation, we often talk about reducing "waste." Yet, many of us are paying a massive "Cognitive Tax" every time we switch between AI models to refine a complex prompt or stress-test a new instructional framework. You might be using one model to apply the CREATE formula to an estimation task, then switching to another for a second opinion on the project documentation. But the moment you switch, the context breaks. You become the human-bridge, manually re-explaining the project goals to a new interface. To solve this, I’ve refined a systematic "Context Switcher" designed for high-stakes professional workflows:




  • Precision Extraction: It moves beyond simple scraping to identify the exact structure of your professional dialogue—User intent, AI analysis, and even the names of attached documentation.

  • The Semantic Bridge: It preserves the "Instructional Design" nuance. If you have spent 30 minutes fine-tuning a prompt for an Agile mobile app project, this script ensures that specific context travels with you.

  • Agile Logic: It maintains the turn-by-turn history of your strategy, from initial brainstorming to the final estimation framework.

  • Zero-Friction Handoff: With one click, the script captures the history, opens the next platform, and auto-pastes the entire strategic context directly into the input area.



In Learning Design and Agile Coaching, efficiency is about more than just speed—it’s about maintaining the integrity of the process. We shouldn't be wasting time being "digital couriers" for our data. If you are orchestrating complex AI workflows to improve team performance, stop being the bridge. Let the system handle the context so you can stay focused on the Learning Architecture. Let’s keep the context alive and the waste at zero. #AgileCoaching #LearningDesign #InstructionalTechnology #AgileEstimation #DigitalTransformation #Productivity #EdTech #ProjectManagement #GenerativeAI


Please login or join to reply

Content ID:
ADVERTISEMENTS

"If at first you don't succeed, try, try again. Then quit. There's no use being a damned fool about it."

- W. C. Fields

ADVERTISEMENT

Sponsors