InformationWeek Podcast: Coordinating Crunch Time Across the Company
Description
What happens when companies have new releases on deck, and it is clear that the dev team is spread too thin?
Teams are always under pressure to deliver, but what if a project calls for overtime across the organization? What happens if those teams are pulled in competing directions?
When major projects are at stake, development teams may face a less-than-ideal circumstance: a race to meet deadlines with near-mandatory overtime.
Such “crunch time” can mean team members get pulled in different directions with little relief in sight until the project is done.
Under such circumstances, CTOs must prioritize where development teams focus, but what happens if other IT resources also need urgent support? New software and apps may need to be delivered, yet existing apps could still need attention.
In this episode of the podcast, Ken Ringdahl, CTO of Emburse, and Larissa Schneider, COO and co-founder of Unframe AI, discuss what happens when teams are spread thin and must deliver, and how they can work to avoid future periods of crunch time.
They also navigated the “Questionable Ideas ‘R’ Us” tabletop exercises, helping the fictional company address its crunch time issues.
United States
