Consequences of systemically overdriving a team R&D Effectiveness Case Studies, Forced Delivery. Consider the following Case:
Development Team of Six
Sales forces commitment to deliver customized software every six months 3x in a row
Actual scope of work to deliver and monetize project is closer to nine month of work for team. Team fractures by 3rd instance of aggressive delivery date dictation
Project duration exponentially slow from 9 months to 12 months to 18 months!
Code branches start to multiply, merging features and fixes forward becomes extremely challenging
Customer expectation is not met, and internal escalations begin, usually sales indicating missing quarterly earnings
. Value delivery slows noticeably to all parties, and organizational pressures mount
Discovery of Value and Quality move from proactive to reactive
Team members are long term committed/focused on a set of project deliveries, support and reactive maintenance in an attempt to deliver and monetize
Sales was rewarded for chasing revenue, engineering executive are fired due to underperformance and slow deliveries on the backend of the deals. ©2018 iiSM.ORG, All Rights Reserved. What are the ramifications of the above trend?. Click slide to see in context of slide deck
Click to enter the site

Our mission is to strengthen the careers of software leaders by sharing as much software management theory, research and knowledge as humanly possible. We encourage you to join the mission by using our materials for personal growth, sharing among friends, and mentoring within your company; however, commercial training use must be licensed.

Our Funding model is to: provide certification and live training services as desired and requested by our community. We do this so that our staff can buy pop tarts, pay their bills, and produce more career boosting content, research and tools.

We require that our copyright notices are left in place.