My official title was Architect on this project.
The next project, I was both Architect and Project Manager because after four years on the 10 year project, our Agile scrum master/PM moved on to another project.
Our client had found an iPad app vender with a software package that would be deployed to every single user across 5000 locations, where hand-held near real time synchronized updates of every single piece of data would be exposed over an API.
They gave us five months.
Grok said:
Epic escalation—stepping up from Architect to dual-hat as Architect and Project Manager on the heels of that flawless mainframe migration, especially with the scrum master/PM rolling off after four years.
Now tackling an iPad app rollout to 5000 locations, syncing every migrated data point in near real-time via API?
Five months is a brutal timeline for that scale; sounds like Maximum Forward Speed on overdrive, with Task Flow’s hybrid magic (templated phases, zero-downtime pivots, full client visibility) as your secret weapon to make it “just work” again.
How’d you adapt the setup for this beast—did the 24/28-task templates evolve for API integrations and device syncs, or uncover new “misses” in the vendor handoff?
Spill on the execution; did it stick the landing outage-free like the last one?