The company had acquired another company in the logistics space that had a large backlog of committed changes to the product.\u00a0 Many of these commitments were made without documentation or technical feasibility evaluation.\u00a0 The dev team ran with no process and little to no quality assurance testing before going live.\u00a0 Customers were leaving, and there was a lawsuit looming and little understanding of how to turn things around.<\/span><\/p>\n

The leaders of the original company were no longer involved with the product.\u00a0 The product was considered\u00a0 a loss leader with the goal of migrating the customers to a new platform once parody of functionality was achieved.\u00a0 The development team didn\u2019t have a standard software delivery lifecycle.\u00a0 The business had no view into technology capacity, so they committed to monthly delivery of everything that came in expecting technology to deliver.\u00a0 Technology felt they had no choice but to accept everything the business requested.<\/span>\u00a0<\/span><\/p>\n

$\"Jenni$

Jenni Crenshaw, SaaS Company Senior Vice President<\/p><\/div>\n

Working for the C suite and specifically the CTO, Jenni was asked to evaluate the stateside leader of the team for his ability to turn the team around.\u00a0 It was determined that he didn\u2019t have a deep understanding of software delivery processes and would require training in what agile is and how to work with business counterparts to be successful.\u00a0 A plan to replace him was started but he quit the next week.\u00a0 Jenni was asked to take over the team and right the ship, putting her initial focus on the dev team.\u00a0\u00a0<\/span>\u00a0<\/span><\/p>\n

Jenni took over the week of a monthly release, so she began by spending a week watching and listening to the team as they prepared for their release.\u00a0 The release went in with defects on 50% of the functions released.\u00a0 This was due code that had never been tested.\u00a0 It was the teams process to \u201ctest as much as they could, then go live.\u201d\u00a0 She immediately implemented a rule that no untested code would go to production.\u00a0 Jenni took some dev capacity and realigned it to build a regression suite which the platform had never had.\u00a0 She then developed a capacity model and had the backlog of work estimated in points by dev function.\u00a0 Jenni equally forced the business side to prioritize their requests and used the two pieces of information to lay out releases.<\/span>\u00a0<\/span><\/p>\n

Concurrently, Jenni sat in on customer calls with the business to understand the biggest issues, finding missed commitments and expectations with code quality.\u00a0 Release 2 went down to 5% code defects in production.\u00a0 Jenni put in weekly touch points for updates, prioritization, and process improvements. The company began telling customers the improvements made and resetting expectations on delivery dates.\u00a0 By month three everything was up to full capacity, delivering clean code and the team could negotiate release cycles with the business without Jenni.<\/span>\u00a0<\/span><\/p>\n

Thirdly, during this time Jenni instituted daily standups with the full team and identified three top players on the team who she met with one-on-one daily.\u00a0 The goal was not only to right the ship but to have it run independently.\u00a0\u00a0 By investing in these resources, progress to that outcome was being made.\u00a0 At that point, the team was functioning well, and the quality was up, but the threat of a lawsuit still loomed due to missed commitments.\u00a0 Jenni asked to stay with the team for another three months to focus on righting the P&L and managing the lawsuit threat.\u00a0 She had a suspicion that the P&L could be realized with a few changes.\u00a0 By evaluating the last three months of data on where capacity had been spent, she identified 3 points in one contract that took up 25% of the capacity and had less than 10% advancement in 3 months.\u00a0<\/span>\u00a0<\/span><\/p>\n

With a laser focus on those 3 points, Jenni established a tiger team of members inside and outside the team bringing in the top talent from across the company.\u00a0 Within a month, they could confidently say that these three points would not be able to be delivered without significant technology investments in a loss leader platform.\u00a0\u00a0<\/span>\u00a0<\/span><\/p>\n

Jenni developed a proposal and went to the CEO to recommend negotiation out of those commitments.\u00a0 By impacting only one customer and only on three requirements, all other commitments could be met within the promised timelines.\u00a0 After much discussion of the analysis, the decision was made to move forward with the recommendation.\u00a0 In the end, Jenni had taken the worst performing dev team to the best performing dev team in the company in just three months.\u00a0 In six months, she stabilized the P&L and avoided a lawsuit for the company.\u00a0 Her drive for analysis and problem solving were the things that pushed her to deliver on this one.\u00a0 She knew the dev team would turn around with a focus on good agile processes, mentoring, and coaching the team to understand their responsibilities.\u00a0 However, it was her focus on the bigger picture and what was happening to the company that led her to identify and turn around the P&L issue.<\/span>\u00a0<\/span><\/p>\n