As the team begins to execute on the schedule, some software related tasks will seem more complicated than originally estimated. If the estimates changed substantially, it’s best to meet with key stakeholders and discuss solutions that will be “good enough”. You’re looking for solutions that are:
- Simple to implement.
- Quick to implement.
- Meet stakeholder requirements.
The big drawback to this approach is that this solution may not turn out to be something that can scale up or serve a larger number of users. Ways to mitigate this are
- Refer to an architect
- Understand best practices
- Conduct what-if scenarios based on the way users use or may use the product.
In my experience, the benefits of seeking a simple, hopefully elegant solution outweigh the downside of creating a brittle solution.
Need help guiding your teams to completing a project? Email us: firstname.lastname@example.org