Hello!
For a larger company that manufactures wooden windows, we developed an extensive iPad iOS application for optimizing their internal processes (measurements, installation, etc..). The development of the application went smoothly and the project was completed successfully. However, we received a new order from our client to upgrade the application with new features/functions. Some of the new functions which they require are special and unfortunately, we can't estimate exactly how much further coding and development is needed. Of course, the client's desire is to have a fixed price offer.
Since we do not have a lot of experience in the field of estimating the scope for unknown work/functions we want to be sure before we give our client a new offer. So help is needed - we're looking for an expert who will help us with the consultation about how to approach r&d for unknown tasks, how to estimate the project, how to explain to client etc. This knowledge will be also needed for future projects.
Thanks!
Valentin
Hi Valentin,
Have you considered splitting the research phase and the development phase? You can quote a fixed amount for the research phase (I'm sure you can estimate this in weeks and take the hit if you go over). You can say to the client that you will quote the development once the research phase is over.
Plus, they can take the research phase output to other providers if you do not or cannot do the work or the quote is too much.
Call me to discuss further if it helps.
Kind regards
Stuart
Hi there!
Approaching the R&D for unknown tasks will always have that element of unknown to it, however, the approach I take, that works best for me is:
1. Have a developer estimate the number of hours they think it will take to implement that piece of functionality (then you can convert these hours into a rate)
2. Add a contingency budget into the fixed price, so that it is something you call fall into should the unknown work piece go over its estimated hours (a typical contingency budget is around 10% of the overall project budget)
3. Be clear on your communications with the client, that could be as simple as saying "We've not come across a request for this functionality before, as such, we aren't too clear on the amount of work thats fully involved"
4. The more unknowns/uncertainty around the project, the higher the contingency budget
I'm Shay by the way! I have run some major projects across the software industry, working with Team Visionary, I have had the privilege to lead major successful projects for Google, Atlassian and OnePlus.
I hope this helps you, if you do require further assistance, I would love to jump into a call and provide you with support.
Hello Valentin,
I appreciate the detailed context you've provided regarding your project. Based on my extensive experience as a Senior Solutions Consultant, particularly in API architecture and development, here's a structured approach to help you estimate and charge for new app functions effectively.
Step-by-Step Approach to Estimating and Charging for New App Functions:
1. Requirement Analysis
Gather Detailed Requirements: Before you can estimate, it's crucial to have a detailed understanding of the new features and functions required. Arrange a meeting with the client to gather as much information as possible about their needs and expectations.
Categorize Features: Break down the new functions into categories such as front-end, back-end, API integration, etc. This will help in organizing the work and assigning accurate time estimates.
2. Research & Development for Unknown Tasks
Conduct R&D Sessions: For special functions that are new or unknown, allocate specific R&D sessions. This involves researching potential solutions, prototyping, and validating the approach.
Time Boxing: Set a fixed amount of time for these R&D activities to avoid spending excessive time on uncertain tasks. Document the findings to provide transparency to the client.
3. Estimate Effort and Time
Use Historical Data: If you have previously completed similar tasks, use that data to inform your estimates. Look at how long similar features have taken and adjust for complexity.
4. Break Down Tasks
Task Breakdown: Divide each feature into smaller tasks. For example, a new feature might include designing, coding, testing, and deployment. Estimate the time required for each sub-task.
Use Estimation Techniques: Techniques like Planning Poker, T-shirt sizing, or the PERT method can help in getting a more accurate estimate. Involve your development team in the estimation process for better accuracy.
5. Risk Assessment
Identify Risks: Consider potential risks that might impact the development time, such as technical challenges, dependency on third-party services, or scope changes.
Add Buffer Time: Include a buffer in your estimates to account for unforeseen issues. Typically, adding a 10-20% buffer is standard practice.
6. Fixed Price vs. Time & Material
Fixed Price Model: This model is suitable when the project scope is well-defined. However, it requires accurate estimation and clear requirements. Any scope changes should be handled through change requests with additional charges.
Time & Material Model: This model offers flexibility for projects with uncertain or evolving scopes. It allows billing based on the actual time and resources spent.
7. Communication with Client
Transparent Communication: Keep the client informed about the estimation process and any assumptions made. Provide a detailed breakdown of the estimated time and cost.
Educate the Client: Explain the complexities involved and why certain tasks may take longer. This helps in setting realistic expectations and justifying the cost.
8. Documentation and Tools
Use Estimation Tools: Tools like JIRA, Trello, or Asana can help in documenting tasks, tracking time, and managing the project.
Detailed Proposal: Prepare a comprehensive proposal that outlines the scope, estimated time, cost, payment terms, and any assumptions or exclusions.
Example Breakdown:
Let's say the client wants to add a new feature for real-time data synchronization.
Requirement Analysis: Understand the data flow, frequency of synchronization, and security requirements.
Research & Development: Prototype the synchronization mechanism.
Task Breakdown:
Design: 8 hours
Development: 20 hours
Testing: 12 hours
Deployment: 4 hours
Risk Assessment: Identify potential latency issues or data conflicts.
Buffer Time: Add 10% buffer, resulting in 4.4 hours.
Total Estimate: 48.4 hours. If you charge $100/hour, the fixed price would be approximately $4840.
Conclusion
By following this structured approach, you can provide accurate estimates and justify your charges for new app functions. This method not only helps in setting realistic client expectations but also ensures that you cover all aspects of the development process.
If you need further assistance, feel free to schedule a call. I'm here to help you navigate these complexities and ensure the success of your project.
Best regards,
James
