Date: July 09, 2025
Update: I am terribly sorry I am bad at updating this. It’s a learning curve, okay!? The most recent update is that we are down to 50 items on that 220+ item list from a month ago. There are still some critical errors on the system that impact your job, which is why we still cant release to the new beta team.
We migrated the list from excel to Slack and it seems the team finds this change easier to manage. We provided the team an internal deadline to complete these last items. However, I am unable to share that deadline here.
Process: Finishing off the final punch list. 50 items left.
Impact on development: +1% on back-end. Staying the same on front-end.
Date: June 10, 2025
Update: Beta 1 group was a success with 220 items reported to the team. We will begin knocking off these items from the punch list, and hopefully getting the second beta team in the system soon. We were not expecting the amount of items to be reported, some really small like a misaligned button, etc..
We changed the reporting type to include critical versus non-critical so that the team puts a priority on critical, and when they can make it happen, fix the non-critical.
Process: Finishing off the final punch list.
Impact on development: -3% in development, -2% in front-end.
Date: May 16, 2025
Update: Beta group 1 wrapping up. We are at internal review, creating documentation, training videos, new website, and training/onboarding schedule. Once this phase is complete, we should have the first design beta group started. Look out for an email here shortly.
Process: internal review > beta launch.
Impact on development: None to report.
Date: April 21, 2025
Update: We are super excited to announce that we finally have the first official beta group in indema. This is a third-party company that is tasked with checking security, penetration testing, and ensuring that the system works as it should to ensure we are in compliance with many different laws. We also have our final punch list from the small beta folks we added in the beginning of April. Our team is almost done with this final punch list. Once that is complete, our back-end team will finalize the API calls from that finished punch list. We will then go to an internal review for a few days to catch any last minute things that are critical before we let the first beta designers in the system. We appreciate your patience SO much through this transition. It’s been a long, rough road full of sweat and tears, but we are almost there.
Process: Final punch List > internal review > beta launch.
Impact on development: None to report.
Date: April 4, 2025
Update: Back-end development is nearly complete with just a focus on ensuring that we connect every API endpoint. Development on front-end yielded a lot of improvements since March 1. Small beta team reported their final list of improvements that we are now currently working on.
Process: Finalize the front-end development changed ordered by beta team, and then go internally to ensure those fixes are complete and schedule a launch date.
Impact on development:
+3% change complete on back-end.
-1% change complete on front-end.
Date: March 1, 2025
Update: We added a few of our beta testers to the system to test the already completed modules. Testing updates from that team are expected every week, with those improvements happening to the provided feedback shortly after. Fine-tuning how this is done on our side, but are confident that we can just focus the following week on those pieces of feedback, while the other half of the dev team focuses on the other modules currently in progress.
Process: Nothing to report.
Impact on development: Nothing to report.
Date: February 25, 2025
Update: Migration to the new AWS system is fully complete and stable as we monitored it the past few days. We are finalizing some details on the front-end UI, with me actually dipping my toes in development to help the team out a bit. Back-end had some setbacks during migration for 2 modules that our lead developer is taking care of but does not impact deliverability with indema 4, nor performance.
Some good news: we have a live server where I can login to an account. One step closer to launching, but of course have to get to that 99%. Not shooing for 100, but close to it.
Process: Nothing to report.
Impact on development: Nothing to report.
Date: February 20, 2025
Update: Looking at the Google cloud compute numbers so far, we’ve decided that we have to switch [back] to AWS servers. Not only are there fundamental issues with Google cloud when it comes to how it’s computed, but for indema’s growth we think it is critical for the change back to something more stable. Further, AWS has been in the cloud computing space longer, leading to a more extensive and diverse portfolio of services. This is particularly appealing to us with complex or specialized needs.
Further, AWS has a very large and mature ecosystem. This means that many third party tools (ones that indema depends on for integrations such as QBO, XERO and more), is already designed to work with AWS.
Process:
Migrations started [DONE]>
Forward to security team to implement security [DONE] >
live server testing [DONE as of 2/5/2025]
Impact on development: The only impact this has on development would be the time it takes for our lead developer to set up the new instance with AWS (roughly 1 day).