![wpriders.com - reliable WordPress development
Industry statistics:
Only 36% projects = successful
😢[1] Standish Group 2014, [2] Wellingtone 2017](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
More Related Content
Similar to WordCamp Lausanne 2018 - Pricing WordPress projects with confidence - Marius Vetrici
Similar to WordCamp Lausanne 2018 - Pricing WordPress projects with confidence - Marius Vetrici (20)
Recently uploaded
Recently uploaded (20)
WordCamp Lausanne 2018 - Pricing WordPress projects with confidence - Marius Vetrici
- 1. wpriders.com - reliable WordPress development Pricing WordPress projects with confidence @mariusvetrici marius@wpriders.com Marius Vetrici Ph.D. Founder @ WPRiders Agency
- 2. wpriders.com - reliable WordPress development Industry statistics: Only 36% projects = successful 😢[1] Standish Group 2014, [2] Wellingtone 2017
- 3. wpriders.com - reliable WordPress development Our team estimate error in 2018 = +24,5% Industry best practice +100% or +200%
- 4. wpriders.com - reliable WordPress development 4 reasons to estimate ➡ Price ➡ Clarity ➡ Resource plan ➡ Milestones
- 5. wpriders.com - reliable WordPress development About estimates - It's easy to estimate what you know - 😃 - It's hard to estimate what you know you don't know. (known unknowns) - 😒 - It's very hard to estimate things that you don't know you don't know. (unknown unknowns) - 🙀 -- Jørgensen, M. Grimstad, S. [3]
- 6. wpriders.com - reliable WordPress development The process overview 1. Qualify the Client and Project 2. Pre-scoping phase 3. [optional] Ballpark estimate – for large projects 4. [optional] Paid scoping phase -> delivers a Requirements Document 5. [optional] Discovery phase -> delivers a Micro Prototype 6. Estimate the project 7. Communicate the estimate to the client
- 7. wpriders.com - reliable WordPress development Qualify the Client and Project • Client knows what he wants OR is willing to be consulted • Client is interested in quality of the process and communication • Project size and type is right for us • Client is in tune with our values
- 8. wpriders.com - reliable WordPress development Pre-scoping phase • Understand client initial requirements • Ask questions to clarify details • Understand business context • Understand business goals
- 9. wpriders.com - reliable WordPress development Ballpark estimate – for large projects [optional] Is your budget above or below $X? This could cost between $A and $B or even more.
- 10. wpriders.com - reliable WordPress development Paid scoping phase [optional] • Secure a paid consultancy project • Interview the client & clarify all the details • Write them down • Deliver “Requirements Document” aka “Scope of Work”
- 11. wpriders.com - reliable WordPress development Discovery phase [optional] • Goal: eliminates technical risks, provides visibility and allows us to estimate • Deliverable: A Micro Prototype • Size: 5-20 hours of work • Focus: very narrow, on 1 technical risk only
- 12. wpriders.com - reliable WordPress development Micro prototype case study Project background: create a Learning Management platform where Instructors post their courses and Students book classes. Project uses WooCommerce Bookings. Micro prototype scope: create a LearnCube virtual class using their API and get a link to the virtual class iframe. Previous failed Micro prototype: use WizIQ instead of LearnCube.
- 13. wpriders.com - reliable WordPress development Estimate template
- 14. wpriders.com - reliable WordPress development Estimate the project - steps 1-3 1. Break down project to tasks of max 6h - If task duration > 6h, break down further - If not possible, run a Discovery Phase first 2. Provide a 3 point estimate for every task: - Expected estimate – I’ve previously worked on something similar - Best estimate – Things turn out simpler than they seemed - Worst case estimate – I will need to code everything from scratch - Calculate 3 point estimate = (4 x Expected + Best + Worst) / 6 3. Calculate Dev-Total = SUM(3point-estimates)
- 15. wpriders.com - reliable WordPress development Estimate the project - steps 4-8 4. Add up your coefficient for PM and testing (eg: 20%) 5. Add up your team’s mean estimate error (eg: 29%) 6. Confirm the estimates with a Senior Developer 7. Multiply by hourly rate 8. Communicate the offer to the client
- 16. wpriders.com - reliable WordPress development Things to consider when estimating • Be mindful/present • Make the estimate with the assigned Developer • Make the estimates auditable • Write your Assumptions in the Notes column • Plan for estimates - Quality estimates take time, • Track your historical estimated vs actual times
- 17. wpriders.com - reliable WordPress development Estimate case study #1 Work Safety Management and Reporting platform - WSMR
- 18. wpriders.com - reliable WordPress development
- 19. wpriders.com - reliable WordPress development WSMR platform estimate The drop downs need to have search including on mobile
- 20. wpriders.com - reliable WordPress development Challenge - Drop downs with search on mobile Solution: Micro Prototype to replace Chosen with Select2 in Gravity Forms
- 21. wpriders.com - reliable WordPress development Estimate case study #2 Custom Theme for wprssaggregator.com
- 22. wpriders.com - reliable WordPress development EDD Product Page Discounts
- 23. wpriders.com - reliable WordPress development Pitfall – Drop down with custom HTML and dynamic discounts
- 24. wpriders.com - reliable WordPress development Bad estimate vs mindful estimate
- 25. wpriders.com - reliable WordPress development Conclusion 1 Good estimates = Clarity and Reliability
- 26. wpriders.com - reliable WordPress development Conclusion 2 Be mindful when estimating WordPress Projects
- 27. wpriders.com - reliable WordPress development Conclusion 3 Break down project to 6h max tasks
- 28. wpriders.com - reliable WordPress development Thank you @mariusvetrici marius@wpriders.com Marius Vetrici Founder @ WPRiders Agency
- 29. wpriders.com - reliable WordPress development Any questions? :) @mariusvetrici marius@wpriders.com Marius Vetrici Ph.D. Founder @ WPRiders Agency
- 30. wpriders.com - reliable WordPress development Resources [1] Standish Group, Chaos Report 2014, https://www.standishgroup.com/sample_research_files/CHAOSReport2014.pdf [2] Wellingtone 2017, The State of Project Management Survey, http://www.wellingtone.co.uk/wp- content/uploads/2017/03/The-State-of-Project-Management-Survey-2017-1.pdf [3] Jørgensen, M. Grimstad, S. "How to Avoid Impact from Irrelevant and Misleading Information When Estimating Software Development Effort". [4] https://en.wikipedia.org/wiki/Cone_of_Uncertainty [5] Fazar, W., Program Evaluation and Review Technique, The American Statistician, Vol. 13, No. 2, April 1959, p.10, ISSN: 0003-1305. [6] https://chrislema.com/estimating-without-requirements/ [7] https://www.joelonsoftware.com/2007/10/26/evidence-based-scheduling/ [8] Kwak Y.H., Ingall L. - Exploring Monte Carlo Simulation Applications for Project Management, Risk Management, Vol. 9, Nr. 1, 2007, pag. 44-57, ISSN: 1460-3799.
Editor's Notes
- Finish reinstalling my computer in max 1 hour OR honey I’ll be ready in 5 minutes. And later – hey, I told you I’ll be ready in 5 minutes. Why are you calling me every half an hour?
- Poor estimation during the planning phase continues to be the largest (32%) contributor to IT project failures. Source: PwC 15th Annual Global CEO Survey, 2012. Only 37% of teams in the U.K. reported completing projects on time more often than not. (Source: Wellingtone)
- Estimates are hard. Raise hand who consider is good with software estimates.
- See [2] https://en.wikipedia.org/wiki/Cone_of_Uncertainty
- Break down the entire project to small tasks of maximum 6 hours each. Make sure you include in your estimate activities like initial setup of the development environment, deployment, and others. Ask the developer that will be working on the project (or a Senior Developer) to provide a 3 point estimate for every task in the list. Include an expected, best case and worst case estimate for every task. Make sure you are mindful (aka present) when breaking down the project/design to tasks. This means, you are very attentive to every detail in the provided design or specification. Expected - here you assume you will use a specific WordPress function, or code snippet or plugin that you’ve used before. Make sure you write down your assumptions in the Assumption Notes column. Best case - here you assume that the above chosen solution will work straight away and there will be no difficulties. Worst case - here you assume you will need to fully code by hand that feature; there will be no plugin to rely on, you will have to write everything from scratch. Make sure you write down your assumptions in the Assumption Notes column. If a task is estimated at more than 6h (in any of the Expected/Best/Worst case columns), break it down further to smaller tasks. The Best and Expected estimates should be maximum 6 hours. If you need to put more than 6 hours, then that's a sign that you don't know what's in that task. In this case, you need to break down that task to smaller tasks, each having max 6 hours. If it is not possible to break down a task into smaller max 6h tasks, run a “Discovery phase” and create a micro prototype to eliminate the risks and gain clarity (see point #5 above). Add up the values and calculate the total. Add your project management (which includes testing) coefficient on top of the total. Know your team’s mean estimate error from your last year and apply it on top of the total. See [3] PERT Equation
- Break down the entire project to small tasks of maximum 6 hours each. Make sure you include in your estimate activities like initial setup of the development environment, deployment, and others. Ask the developer that will be working on the project (or a Senior Developer) to provide a 3 point estimate for every task in the list. Include an expected, best case and worst case estimate for every task. Make sure you are mindful (aka present) when breaking down the project/design to tasks. This means, you are very attentive to every detail in the provided design or specification. Expected - here you assume you will use a specific WordPress function, or code snippet or plugin that you’ve used before. Make sure you write down your assumptions in the Assumption Notes column. Best case - here you assume that the above chosen solution will work straight away and there will be no difficulties. Worst case - here you assume you will need to fully code by hand that feature; there will be no plugin to rely on, you will have to write everything from scratch. Make sure you write down your assumptions in the Assumption Notes column. If a task is estimated at more than 6h (in any of the Expected/Best/Worst case columns), break it down further to smaller tasks. The Best and Expected estimates should be maximum 6 hours. If you need to put more than 6 hours, then that's a sign that you don't know what's in that task. In this case, you need to break down that task to smaller tasks, each having max 6 hours. If it is not possible to break down a task into smaller max 6h tasks, run a “Discovery phase” and create a micro prototype to eliminate the risks and gain clarity (see point #5 above). Add up the values and calculate the total. Add your project management (which includes testing) coefficient on top of the total. Know your team’s mean estimate error from your last year and apply it on top of the total. See [4] Chris Lema See [5] & [6]
- We ran a discovery phase for testing if the drop down with search works fine on mobile devices using Gravity Forms. Chosen did not work, but Select2 worked fine.
- Unknown unknowns
- Check all the layers in PSD. In our case: custom HTML dynamic calculation of the discount in back-end there were hundreds of variants defined; we were asked to only estimate the custom drop down should also work inside a sticky sidebar