Imagine that you have already validated a possible need for a product and you start to create the first Minimum Viable Product, that's not a Prototype.
Even though you have less risk, you still need to try a lot of stuff. The system will be changing fast and often, and sometimes you need to replace the whole system.
In this context, do you think that investing in the next points is a waste or actually worth to do:
- Continuous Delivery System
- Good practices
- Automated testing
- Monitoring
- Analytics
If you think it's not worth at an early stage, then when you think it's worth?
Top comments (4)
in projects where there's no prototype and there's only a vague idea of what the end result will look like, my team (typically) follows this path:
note: we mainly do web apps with a js client and c# rest server.
this is not a holly grail for us and we evaluate our processes depending on the project/task at hand. but the above has served us well so far. and the only pattern/ practise we ask every team member to follow religiously is KISS. if they submit PRs with too much complexity they'll be asked to redo that feature simplified if feasible.
Thanks for sharing! :)
I would say you work in a quite complete team, with different roles and people involved, and which each person have their own responsibilities during the development and delivery.
In your scenario, I miss which is the time between you initialize the Git Repository and the first v1.0.0 is released, an average number.
On the other hand, to me it's strange the next point:
If I understood it correctly, you first release (the application is live and with users) and then you start writing test. Once you have both, v1 out and tests, you start adding the monitoring and analytics.
Why not do that during the development? Why not setup the monitoring since the beginning and also add some testing (maybe not a 90% coverage)
trunkbaseddevelopment.com/
IMHO and experience, I have seen that introducing those practices and methodologies at the early beginning really pays off.
It was hard to see the benefits at the early beginning, as an engineer, having as much as automated as possible really helped me deliver faster and with confidence.
Under a context of so much pressure and changing environment, having a backup as a Continuous Delivery System combined with an enough trustful automated testing suite was awesome. We were able to accept more changes and deliver with confidence that the important stuff didn't break too often.