This document discusses techniques for software project estimation. It recommends providing estimates as ranges rather than specific numbers, and always clarifying what an estimate will be used for. It emphasizes aggregating independent estimates, using past project data to calibrate estimates, and not negotiating estimates or commitments. Key techniques include decomposing work into independently estimable units, using the "law of large numbers" for accuracy, and re-estimating regularly based on actual project velocity. Overall, the document provides guidance for creating estimates that are useful without being overly precise commitments.
Agile Patterns: Agile Estimation
We’re agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will consist of review of the problem with estimation in projects today and then an overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, team velocity, how to apply them all to estimation and iterative re-estimation. We will take a look at the cone of uncertainty and how to use it to your advantage. We’ll then take a look at the tools we will use for Agile Estimation, including planning poker, Visual Studio Team System, and much more. This is a very interactive session, so bring a lot of questions!
This August Scrum Breakfast, we have a new speaker - Mr. Pedro Gonzalez - Scrum Master at TINYpulse.
He will bring us an interesting topic about Agile estimation using story points, giving some tips on why relative estimations are far better than absolutes, why we shouldn't spend too long in details, and other issues he has experienced himself with his team.
Estimating with MAGIC Approach – Measure, Analyze, Improve and Control without ‘Guess’ work
#) Measure & Analyze using ‘Story Point Matrix’ based on Functional & Technical Analysis
#)Improve & Control using Statistical Data Modeling based on Empirical Data extracted from agile project management tool
Introduction to Agile Estimation & PlanningAmaad Qureshi
Presented by Natasha Hill & Amaad Qureshi
In this session, we will be covering the techniques of estimating Epics, Features and User Stories on an Agile project and then of creating iteration and release plans from these artefacts.
Agenda
1. Why traditional estimation approaches fail
2. What makes a good Agile Estimating and Planning approach.
3. Story points vs. Ideal Days
4. Estimating product backlog items with Planning Poker
5. Iteration planning - looking ahead and estimating no more than a few week ahead.
6. Release planning - creating a longer term plan, typically looking ahead, 3-6 months
7. Q&A
Agile Patterns: Agile Estimation
We’re agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will consist of review of the problem with estimation in projects today and then an overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, team velocity, how to apply them all to estimation and iterative re-estimation. We will take a look at the cone of uncertainty and how to use it to your advantage. We’ll then take a look at the tools we will use for Agile Estimation, including planning poker, Visual Studio Team System, and much more. This is a very interactive session, so bring a lot of questions!
This August Scrum Breakfast, we have a new speaker - Mr. Pedro Gonzalez - Scrum Master at TINYpulse.
He will bring us an interesting topic about Agile estimation using story points, giving some tips on why relative estimations are far better than absolutes, why we shouldn't spend too long in details, and other issues he has experienced himself with his team.
Estimating with MAGIC Approach – Measure, Analyze, Improve and Control without ‘Guess’ work
#) Measure & Analyze using ‘Story Point Matrix’ based on Functional & Technical Analysis
#)Improve & Control using Statistical Data Modeling based on Empirical Data extracted from agile project management tool
Introduction to Agile Estimation & PlanningAmaad Qureshi
Presented by Natasha Hill & Amaad Qureshi
In this session, we will be covering the techniques of estimating Epics, Features and User Stories on an Agile project and then of creating iteration and release plans from these artefacts.
Agenda
1. Why traditional estimation approaches fail
2. What makes a good Agile Estimating and Planning approach.
3. Story points vs. Ideal Days
4. Estimating product backlog items with Planning Poker
5. Iteration planning - looking ahead and estimating no more than a few week ahead.
6. Release planning - creating a longer term plan, typically looking ahead, 3-6 months
7. Q&A
This presentation includes an overview of the various estimation techniques used in Agile projects. I've also put in a slide for explaining the importance of business value for Agile requirements. A simple mechanism on capacity planning before weaving it all together to come up with a reasonably foolproof plan.
This is a short introduction to the practice of Sprint Planning in Scrum. It would be useful for people new to Scrum or Agile. For more, comment or write to read my blog : http://agilediary.wordpress.com/
Agile development works well in small teams. But we encounter problems when Scrum is applied to other teams and the rest of the organisation. Large Scale Scrum (LeSS) can help. This slide deck explains why.
Scrum Prioritization Techniques PowerPoint Presentation Slides help you represent the division of large projects into achievable tasks. Use this PPT deck to represent your agile software development approach. Communicate the agile project details and scrum team composition with the visual aid of a well-structured diagram. Demonstrate the goals and phases of your agile project delivery. Explain waterfall technique, scrum-fall, lean, or other methodology for agile application development. The data visualizations featured in this PowerPoint slideshow simplify the translation of agile architecture, and agile automation process. Educate the audience about the project prioritization techniques like MoSCoW, Kano model, and the relative weighting method. Use this PPT presentation to highlight the key priority areas in agile project management. Another important aspect of managing projects is cost. Showcase the agile software project cost using a neat tabular format. You will also get access to the agile program management dashboard diagram to track development. So, smash the download icon and begin instant personalization. Our Scrum Prioritization Techniques PowerPoint Presentation Slides are explicit and effective. They combine clarity and concise expression. https://bit.ly/2IHexRe
Why estimate user stories using poker planning? What’s the advantage of relative estimation? Why leverage Fibonacci series?
These slides explore the reasons for relative estimation using Fibonacci through a collection of exercises and illustrations.
Slides assume a basic understanding of user stories and poker planning.
Originally presented as an Agile 101 at Agile New England in May 2023.
Jumping into solutions is only human. And it is a perfect approach when dealing with simple, obvious problems. But as soon the challenges become more complicated, and usually, all the business questions do, moving into the solution space too fast will only lead to poor results, wrong focus and to solving a problem that is not worth the investment in the first place.
These are some of the reasons why we developed the Design Sprint 3.0 approach. In Design Sprint 3.0 we focus mostly on framing the right problem and ensuring the stakeholder's buy-in.
Here's how the process goes...
My main goal is to share and make you experiment some of the techniques that I use when transforming teams into high-perfoming agile teams, by providing you with four (4) different ways to estimate projects in Agile.
Estimation is associated with Fear, Uncertainty and Death marches. Most of us would rather not estimate. Yet, sometimes we do need estimates and commitments, even on "estimation-less" projects. Play a series of estimation games to experience how different techniques deliver very different results. Learn a few simple rules that turn you into a reliable estimator. But correct estimates aren't enough. See what else is required to deliver on your promises. Learn to deal with the destructive games people play with estimates. Estimating can be Fun, embracing Uncertainty and Delivering.
This presentation includes an overview of the various estimation techniques used in Agile projects. I've also put in a slide for explaining the importance of business value for Agile requirements. A simple mechanism on capacity planning before weaving it all together to come up with a reasonably foolproof plan.
This is a short introduction to the practice of Sprint Planning in Scrum. It would be useful for people new to Scrum or Agile. For more, comment or write to read my blog : http://agilediary.wordpress.com/
Agile development works well in small teams. But we encounter problems when Scrum is applied to other teams and the rest of the organisation. Large Scale Scrum (LeSS) can help. This slide deck explains why.
Scrum Prioritization Techniques PowerPoint Presentation Slides help you represent the division of large projects into achievable tasks. Use this PPT deck to represent your agile software development approach. Communicate the agile project details and scrum team composition with the visual aid of a well-structured diagram. Demonstrate the goals and phases of your agile project delivery. Explain waterfall technique, scrum-fall, lean, or other methodology for agile application development. The data visualizations featured in this PowerPoint slideshow simplify the translation of agile architecture, and agile automation process. Educate the audience about the project prioritization techniques like MoSCoW, Kano model, and the relative weighting method. Use this PPT presentation to highlight the key priority areas in agile project management. Another important aspect of managing projects is cost. Showcase the agile software project cost using a neat tabular format. You will also get access to the agile program management dashboard diagram to track development. So, smash the download icon and begin instant personalization. Our Scrum Prioritization Techniques PowerPoint Presentation Slides are explicit and effective. They combine clarity and concise expression. https://bit.ly/2IHexRe
Why estimate user stories using poker planning? What’s the advantage of relative estimation? Why leverage Fibonacci series?
These slides explore the reasons for relative estimation using Fibonacci through a collection of exercises and illustrations.
Slides assume a basic understanding of user stories and poker planning.
Originally presented as an Agile 101 at Agile New England in May 2023.
Jumping into solutions is only human. And it is a perfect approach when dealing with simple, obvious problems. But as soon the challenges become more complicated, and usually, all the business questions do, moving into the solution space too fast will only lead to poor results, wrong focus and to solving a problem that is not worth the investment in the first place.
These are some of the reasons why we developed the Design Sprint 3.0 approach. In Design Sprint 3.0 we focus mostly on framing the right problem and ensuring the stakeholder's buy-in.
Here's how the process goes...
My main goal is to share and make you experiment some of the techniques that I use when transforming teams into high-perfoming agile teams, by providing you with four (4) different ways to estimate projects in Agile.
Estimation is associated with Fear, Uncertainty and Death marches. Most of us would rather not estimate. Yet, sometimes we do need estimates and commitments, even on "estimation-less" projects. Play a series of estimation games to experience how different techniques deliver very different results. Learn a few simple rules that turn you into a reliable estimator. But correct estimates aren't enough. See what else is required to deliver on your promises. Learn to deal with the destructive games people play with estimates. Estimating can be Fun, embracing Uncertainty and Delivering.
Every year, software companies spend a huge amount of time and effort estimating large projects, and still end up regularly missing the mark - often by huge amounts. What the heck is going on? With all of the planning poker, and PI planning, and #noestimates, why isn't this figured out yet?
In this talk, we'll dive into probability theory and psychology to discover some of the common underlying causes for a lack of predictability. Once we understand why the world is so uncertain, we'll talk about how we can live with our estimation failures, while still thrilling our customers and maintaining enough predictability to succeed as an organization.
I read, reviewed and digested the excellent The Art of Estimation by Steve McConnell and presented back what I'd learned about software estimation to the team.
Data Visualization is widely used in industries in info-graphics design, business analytics, data analytics, advanced analytics, business intelligence dashboards, content marketing. It is the 1st part of 3 part series on data visualization. These techniques will enable you to create a good design UI/UX. It contains r codes useful for programmers to create good visual charts and depict a story to clients, customer, senior management, etc ...
Everyone has been given a 2 paragraph document listing the "scope of services" for a potential project. The client would like an estimate in 48 hours and there are no more details to help you deliver that required fixed bid contract. At the same time, many teams have also been given (or created) a detailed PRD or backlog document and still had a project budget balloon out of control. In this session I would like to discuss the not only the problems associated with estimation and how to avoid them, but more importantly how we can plan for them, turning our estimation process into not only an art, but a science. Well cover how to sell your estimate internally, and arm you with the methodologies to support your numbers. The problem with software estimation The morale The metrics The reality - an estimation metaphor Avoiding Risk Project entry point of sale At what point of the project lifecycle is your first sale? Risk association with point of sale Products in the front, estimations in the back The Elusive Discovery phase How to estimate a discovery How to sell a discovery How to include discovery in a full fixed bid RFP Planning for Risk Estimation types Gut - An art form Comparables - An art/science Factors/formula - A science Contingency Rating systems Formulas Granularity
Agile Experimentation in Everyday Life - A Guide to More Aha! moments by Milo...Bosnia Agile
In the realm of software development, the pursuit of accurate project estimation has been a perpetual challenge. Despite the rise of Agile methods, the specter of inaccurate estimation continues to cast a shadow over projects, leading to missed deadlines, exceeded budgets, and frustrated stakeholders.
Consider this: a groundbreaking study by the Standish Group in 1995 revealed that a staggering 31.1% of software projects were canceled before completion, with over 50% ending up costing nearly twice their initial estimates. Fast forward to the present day, and while Agile has undeniably transformed development practices, the issue of project estimation remains a thorny one.
While Agile projects boast a commendable success rate three times higher than traditional waterfall approaches, over 50% still grapple with time and cost overruns. The question then arises: why has Agile, with its iterative approach and emphasis on collaboration, not completely eradicated the problem of inaccurate estimation?
Agile introduced relative estimation, epitomized by story points, in contrast to the upfront man-day estimations of the past. However, the journey towards accurate estimation has been fraught with challenges. Despite their widespread adoption, story points have often fallen short, leading to counterintuitive outcomes. A case study within a prominent corporation revealed that stories rated lower in complexity took longer to complete than ostensibly more complex ones.
This dilemma underscores a fundamental truth: the challenge of estimation transcends estimation methods; it is deeply rooted in human nature. Our innate biases and tendencies toward optimism color our estimations, rendering them prone to error. To break free from this cycle, a paradigm shift is necessary—one that embraces a data-driven approach.
The answer: actionable agile metrics and probabilistic forecasting. By leveraging historical data, teams can move beyond guesswork toward informed decision-making. These metrics provide nuanced insights into team performance and project dynamics, empowering teams to make accurate predictions about future outcomes.
During this talk/presentation, I will share:
- the results of two studies by the Standish Group (1995, 2020)
- a case study about story points from one US corporation
- what metrics we need to gather as well as how (and why)
- some cool models and tools (through quick demos or screenshots)
In this illuminating talk, we'll demystify agile estimation, drawing from real-world examples and personal experiences. Attendees will gain practical insights into the tools and techniques that underpin effective estimation practices. By the end of the session, participants will be armed with actionable strategies and newfound knowledge to navigate the estimation challenge confidently, ensuring smoother sailing on their Agile journey.
Agile Estimating & Planning by Amaad QureshiAmaad Qureshi
An introduction to Agile Estimating and how it can be used to measure the size and length of work.
Agile estimating & planning is a way of measuring the size and time it takes to complete a task. This technique is used by Agile teams in Enterprise and can be utilised in the same way by Start-ups not just for software but for all areas of the business. In this talk I will show you how estimating & planning works by:
- Writing effective user stories
- Writing tests to validate stories (acceptance criteria)
- Using story points to work out the size of a task
- Estimating using Planning Poker
- Using Story Points to calculate a team’s velocity (speed of work)
- Using a team’s velocity to calculate project length
Three baseline metrics & what they can tell you about your team.Mike Burns
Originally presented at Agile Australia 2017.
Associated blog post - https://www.linkedin.com/pulse/three-baseline-metrics-what-can-tell-you-your-team-mike-burns
Discover how to tailor your metrics to suit you. This guide outlines which metrics a team can start using today to help improve team performance, and allow for the right decisions to be made at the right time.
By looking at cycle time, throughput, and work item size, we discuss what they reveal about a team; how they can be used to make improvements; and how to ensure metrics are used as conversation starters rather than a ‘dreaded monthly report’.
We can also use metrics to help us learn from our experiments. By using the right measures and metrics we can get real data and, more importantly, information that helps us to make the right decisions at the right time.
Vous pouvez ignorerr les controleurs de gestionAgileCoach.net
Présentation de la session "Vous pouvez ignorer les controleurs de gestion, eux ne vous ignoreront pas" about the influence of accounting models on agile and lean
Keynote présentée à Agile grenoble 2013. Comment écrire du mauvais code plus rapidement avec les méthodes agiles. Il est temps de prendre plus de responsabilité pour la qualité de notre travail et nos produits qui affectent la vie de tout le monde.
We talk a lot about "maximizing business value". We ask business people and product managers to prioritise by estimating the business value of user stories. But what exactly do we mean by business value?
Tutorial on how to use the Conflict Resolution Diagram. Presented by Portia Tung and Pascal Van Cauwenberghe at the Mini SPA conference, London, September 2010
Attending a job Interview for B1 and B2 Englsih learnersErika906060
It is a sample of an interview for a business english class for pre-intermediate and intermediate english students with emphasis on the speking ability.
Unveiling the Secrets How Does Generative AI Work.pdfSam H
At its core, generative artificial intelligence relies on the concept of generative models, which serve as engines that churn out entirely new data resembling their training data. It is like a sculptor who has studied so many forms found in nature and then uses this knowledge to create sculptures from his imagination that have never been seen before anywhere else. If taken to cyberspace, gans work almost the same way.
"𝑩𝑬𝑮𝑼𝑵 𝑾𝑰𝑻𝑯 𝑻𝑱 𝑰𝑺 𝑯𝑨𝑳𝑭 𝑫𝑶𝑵𝑬"
𝐓𝐉 𝐂𝐨𝐦𝐬 (𝐓𝐉 𝐂𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬) is a professional event agency that includes experts in the event-organizing market in Vietnam, Korea, and ASEAN countries. We provide unlimited types of events from Music concerts, Fan meetings, and Culture festivals to Corporate events, Internal company events, Golf tournaments, MICE events, and Exhibitions.
𝐓𝐉 𝐂𝐨𝐦𝐬 provides unlimited package services including such as Event organizing, Event planning, Event production, Manpower, PR marketing, Design 2D/3D, VIP protocols, Interpreter agency, etc.
Sports events - Golf competitions/billiards competitions/company sports events: dynamic and challenging
⭐ 𝐅𝐞𝐚𝐭𝐮𝐫𝐞𝐝 𝐩𝐫𝐨𝐣𝐞𝐜𝐭𝐬:
➢ 2024 BAEKHYUN [Lonsdaleite] IN HO CHI MINH
➢ SUPER JUNIOR-L.S.S. THE SHOW : Th3ee Guys in HO CHI MINH
➢FreenBecky 1st Fan Meeting in Vietnam
➢CHILDREN ART EXHIBITION 2024: BEYOND BARRIERS
➢ WOW K-Music Festival 2023
➢ Winner [CROSS] Tour in HCM
➢ Super Show 9 in HCM with Super Junior
➢ HCMC - Gyeongsangbuk-do Culture and Tourism Festival
➢ Korean Vietnam Partnership - Fair with LG
➢ Korean President visits Samsung Electronics R&D Center
➢ Vietnam Food Expo with Lotte Wellfood
"𝐄𝐯𝐞𝐫𝐲 𝐞𝐯𝐞𝐧𝐭 𝐢𝐬 𝐚 𝐬𝐭𝐨𝐫𝐲, 𝐚 𝐬𝐩𝐞𝐜𝐢𝐚𝐥 𝐣𝐨𝐮𝐫𝐧𝐞𝐲. 𝐖𝐞 𝐚𝐥𝐰𝐚𝐲𝐬 𝐛𝐞𝐥𝐢𝐞𝐯𝐞 𝐭𝐡𝐚𝐭 𝐬𝐡𝐨𝐫𝐭𝐥𝐲 𝐲𝐨𝐮 𝐰𝐢𝐥𝐥 𝐛𝐞 𝐚 𝐩𝐚𝐫𝐭 𝐨𝐟 𝐨𝐮𝐫 𝐬𝐭𝐨𝐫𝐢𝐞𝐬."
Falcon stands out as a top-tier P2P Invoice Discounting platform in India, bridging esteemed blue-chip companies and eager investors. Our goal is to transform the investment landscape in India by establishing a comprehensive destination for borrowers and investors with diverse profiles and needs, all while minimizing risk. What sets Falcon apart is the elimination of intermediaries such as commercial banks and depository institutions, allowing investors to enjoy higher yields.
Memorandum Of Association Constitution of Company.pptseri bangash
www.seribangash.com
A Memorandum of Association (MOA) is a legal document that outlines the fundamental principles and objectives upon which a company operates. It serves as the company's charter or constitution and defines the scope of its activities. Here's a detailed note on the MOA:
Contents of Memorandum of Association:
Name Clause: This clause states the name of the company, which should end with words like "Limited" or "Ltd." for a public limited company and "Private Limited" or "Pvt. Ltd." for a private limited company.
https://seribangash.com/article-of-association-is-legal-doc-of-company/
Registered Office Clause: It specifies the location where the company's registered office is situated. This office is where all official communications and notices are sent.
Objective Clause: This clause delineates the main objectives for which the company is formed. It's important to define these objectives clearly, as the company cannot undertake activities beyond those mentioned in this clause.
www.seribangash.com
Liability Clause: It outlines the extent of liability of the company's members. In the case of companies limited by shares, the liability of members is limited to the amount unpaid on their shares. For companies limited by guarantee, members' liability is limited to the amount they undertake to contribute if the company is wound up.
https://seribangash.com/promotors-is-person-conceived-formation-company/
Capital Clause: This clause specifies the authorized capital of the company, i.e., the maximum amount of share capital the company is authorized to issue. It also mentions the division of this capital into shares and their respective nominal value.
Association Clause: It simply states that the subscribers wish to form a company and agree to become members of it, in accordance with the terms of the MOA.
Importance of Memorandum of Association:
Legal Requirement: The MOA is a legal requirement for the formation of a company. It must be filed with the Registrar of Companies during the incorporation process.
Constitutional Document: It serves as the company's constitutional document, defining its scope, powers, and limitations.
Protection of Members: It protects the interests of the company's members by clearly defining the objectives and limiting their liability.
External Communication: It provides clarity to external parties, such as investors, creditors, and regulatory authorities, regarding the company's objectives and powers.
https://seribangash.com/difference-public-and-private-company-law/
Binding Authority: The company and its members are bound by the provisions of the MOA. Any action taken beyond its scope may be considered ultra vires (beyond the powers) of the company and therefore void.
Amendment of MOA:
While the MOA lays down the company's fundamental principles, it is not entirely immutable. It can be amended, but only under specific circumstances and in compliance with legal procedures. Amendments typically require shareholder
Improving profitability for small businessBen Wann
In this comprehensive presentation, we will explore strategies and practical tips for enhancing profitability in small businesses. Tailored to meet the unique challenges faced by small enterprises, this session covers various aspects that directly impact the bottom line. Attendees will learn how to optimize operational efficiency, manage expenses, and increase revenue through innovative marketing and customer engagement techniques.
Affordable Stationery Printing Services in Jaipur | Navpack n PrintNavpack & Print
Looking for professional printing services in Jaipur? Navpack n Print offers high-quality and affordable stationery printing for all your business needs. Stand out with custom stationery designs and fast turnaround times. Contact us today for a quote!
RMD24 | Retail media: hoe zet je dit in als je geen AH of Unilever bent? Heid...BBPMedia1
Grote partijen zijn al een tijdje onderweg met retail media. Ondertussen worden in dit domein ook de kansen zichtbaar voor andere spelers in de markt. Maar met die kansen ontstaan ook vragen: Zelf retail media worden of erop adverteren? In welke fase van de funnel past het en hoe integreer je het in een mediaplan? Wat is nu precies het verschil met marketplaces en Programmatic ads? In dit half uur beslechten we de dilemma's en krijg je antwoorden op wanneer het voor jou tijd is om de volgende stap te zetten.
RMD24 | Debunking the non-endemic revenue myth Marvin Vacquier Droop | First ...BBPMedia1
Marvin neemt je in deze presentatie mee in de voordelen van non-endemic advertising op retail media netwerken. Hij brengt ook de uitdagingen in beeld die de markt op dit moment heeft op het gebied van retail media voor niet-leveranciers.
Retail media wordt gezien als het nieuwe advertising-medium en ook mediabureaus richten massaal retail media-afdelingen op. Merken die niet in de betreffende winkel liggen staan ook nog niet in de rij om op de retail media netwerken te adverteren. Marvin belicht de uitdagingen die er zijn om echt aansluiting te vinden op die markt van non-endemic advertising.
Tata Group Dials Taiwan for Its Chipmaking Ambition in Gujarat’s DholeraAvirahi City Dholera
The Tata Group, a titan of Indian industry, is making waves with its advanced talks with Taiwanese chipmakers Powerchip Semiconductor Manufacturing Corporation (PSMC) and UMC Group. The goal? Establishing a cutting-edge semiconductor fabrication unit (fab) in Dholera, Gujarat. This isn’t just any project; it’s a potential game changer for India’s chipmaking aspirations and a boon for investors seeking promising residential projects in dholera sir.
Visit : https://www.avirahi.com/blog/tata-group-dials-taiwan-for-its-chipmaking-ambition-in-gujarats-dholera/
3.0 Project 2_ Developing My Brand Identity Kit.pptxtanyjahb
A personal brand exploration presentation summarizes an individual's unique qualities and goals, covering strengths, values, passions, and target audience. It helps individuals understand what makes them stand out, their desired image, and how they aim to achieve it.
LA HUG - Video Testimonials with Chynna Morgan - June 2024Lital Barkan
Have you ever heard that user-generated content or video testimonials can take your brand to the next level? We will explore how you can effectively use video testimonials to leverage and boost your sales, content strategy, and increase your CRM data.🤯
We will dig deeper into:
1. How to capture video testimonials that convert from your audience 🎥
2. How to leverage your testimonials to boost your sales 💲
3. How you can capture more CRM data to understand your audience better through video testimonials. 📊
4. # 1: Always give a range Never give them a number
5. # 1: Numbers are for factsRanges are for estimates I estimate “Between 650 and 700m” Or “Between 0 et 4000m” I know it’s 694m (2092 ft)
6. Estimation exercise One result per table Choose one of three collaboration techniques If you can’t choose, let the Post-It choose for you RED Post-It Estimate as a group, come to consensus GREEN Post-It Divide the work among you YELLOW Post-it First estimate individually Then combine the estimates as a group
7. Estimation exercise 1 Surface temperature of the sun (in degrees C) Latitude of Shanghai (in degrees) Surface area of Asia (in km2) Birth date of Alexander The Great (year) Dollars in circulation in the US in 2004 (in $) Volume of the Great American lakes (in litres) Global revenue of “Titanic” (in $) Length of the Pacific coastline (Ca, Or, Wa) (in km) Number of books published in USA, 1776 to 2004 Weight of the largest whale (in tonnes) Time’s up! 10min This quiz is from “Software Estimation” by Steve McConnell (Microsoft Press) (C) 2006 Steve McConnell. Used with permission
8. An estimation joke An engineer, a mathematician and an accountant are sitting at the bar The barman asks: “What’s 68+73 ?” Engineer: 141 Mathematician: 68 + 73 = 73 + 68 Accountant: Usually it’s 141, but what do you want to do with the number?
14. Estimating money (individually) How much money is there in this room? Counting only cash dollars Re-do the estimation, but this time Count the number of people: N Count how much money you have on you: M Estimate how much money the average person holds, based on M: M1-M2 Compute the amount: N * M1 – N * M2
15. What can you count? Number of stakeholders Number of goals Number of events Number of business processes Number of high-level user stories Number of detailed user stories Number of screens ....
16. #4 First try to measure, count and computeEstimate only when necessary
17. Estimating money (in group) Estimate as one group per table Combine individual estimations into a group estimate Planning Poker style: announce estimates, low/high estimators explain, again Take min and max for a range that covers all estimates Take average of min and max for a range that covers much of the estimates ...
18. Aggregate estimates Independent estimators For example, by playing Planning Poker Independent estimation methods For example, by combining: Comparison with previous project Expert estimation Counting high level stories
20. The law of large numbers (or: statistics is on our side, for once) If we estimate with an error of x% The estimate of each scope item will have an error of x% But... Some items will be over-estimated, others under-estimated (maybe....) => The error on the total estimate is < x%
21. The law of 15 Have about 15-20 same-sized elements at each planning horizon Program, Project, Release, Iteration Enough for the law of large numbers to have an effect But not too many, easy to manage
22. #6 Use the law of large numbers Decompose Just enough, just in time
26. Re-estimation and calibration First estimation: Relative estimate (1 point, 2 points, ...) Calibrate with previous projects (16-22 points per iteration) Re-estimate during the project Check if relative sizes are ok Re-calibrate with measured velocity
27. Ensure consistency of relative estimates Build in internal consistency Demonstrated in “XP Game” Analyse large errors in retrospectives Some variance is normal Keep a library of representative reference stories Estimate relative to references Add stories that were mis-estimated!
28. Velocity of the first project Take a similar, finished project Estimate relatively in Story points: N points We know it took M mandays Decide how many mandays per iteration: K Velocity = +/- K * N/M points/iteration Attention: M is complete cost No “Twilight Zone” or “Murky Zone”!
29. #7 Calibrate your estimates with real velocity data Project data > Company data > Industry data
30. Evil Estimation Games “Guess the number I’ve got in my head!” “An awesome team like you can do better than that!” “This time it’ll go so much faster, because we learned so much from the previous project!” “This project will be very different!” “If we just work a bit harder, we’ll increase velocity” “I could code this in half the time!” “If we lower the estimate, the project will be done faster” (this actually works in some circumstances...)
31. Q: Why are there so many pointy haired-bosses? A: because there are so many Dilberts
32. #8 Never negotiate estimates Always question the reasoning and assumptions behind estimates
34. #10 Solve problems together Make assumptions explicit Question assumptions Offer options
35. The Options exercise Estimate of the project: 5-6 months Conference in 3 months We need to make a great impression on prospects I want to show all our functionality Which assumptions are we making? What options can you offer?
36. Roadmap OR Kanban? Our dilemma: Product manager needs to publish a credible long term roadmap for customers, partners and integrators Development team has flow-based process without estimation, planning or velocity tracking We can’t have both, can we? Yes we can!
37. Roadmap AND Kanban Roadmap with customer goals, not features Product Manager estimates value of achieving each goal => priorities of roadmap Product Manager determines budget per goal Quick feasibility check by team Each release, PM and team find a way to achieve release goals within release budget Watch flow, ensure release goals are met
38. Summary Ranges for estimates. Numbers for facts. Always ask what the estimate will be used for Estimation is not Commitment Measure, count, compute before estimating Aggregate independent estimates Use the law of large numbers (large ~= 15) Calibrate estimates with measured velocity Never negotiate estimates Never negotiate commitments Solve problems together
39. Estimation exercise 2 Surface temperature of the sun (in degrees C) Latitude of Shanghai (in degrees) Surface area of Asia (in km2) Birth date of Alexander The Great (year) Dollars in circulation in the US in 2004 (in $) Volume of the Great American lakes (in litres) Global revenue of “Titanic” (in $) Length of the Pacific coastline (Ca, Or, Wa) (in km) Number of books published in USA, 1776 to 2004 Weight of the largest whale (in tonnes) Time’s up! 6 min This quiz is from “Software Estimation” by Steve McConnell (Microsoft Press) (C) 2006 Steve McConnell. Used with permission
40. Answers Sun: 6000° C Shanghai: 31 degrees North Asian area: 44,390,000 km² Alexander was born in 356 BC Dollars in circulation: $719.9 billion Great Lakes: 6.8x10^23 litres Titanic: 1.835 billion $ Pacific Coast: 1293 kilometres Published books: 22 million Whale: 170 tonnes This quiz is from “Software Estimation” by Steve McConnell (Microsoft Press) (C) 2006 Steve McConnell. Used with permission
41. And the winner is? Life is like a box of tasty Belgian chocolates!
46. If you want to know more www.agilecoach.net www.nayima.be blog.nayima.be
Editor's Notes
Portia and Pascal introduce themselves by sharing a bit about their background.
TODO create CRD
We are constantly striving to improve. Give your Gift of Feedback by completing a session retrospective.Everyone take a sheet of paper. Split it into 4 quadrants.In the top left quadrant, note down all the things that went well.In the top right quadrant, note down all the things that went wrong.In the bottom left quadrant, note down your puzzles such as outstanding questions you have as a result of the attending the session.In the bottom right quadrant, note down your lessons learned.