Cynthia is a newly hired software developer at MainFrame, which uses Scrum to manage projects. But she agrees with her coworkers that the company's methodical and deliberate pace is inferior to the quicker, more loosely structured approach of her previous employer, which used Flow. So when a colleague approaches her and asks her to use her impressive background and credentials to advocate for Flow, Cynthia agrees. But after her pilot project produces mixed results, she wonders whether she should proceed with a presentation to the process-improvement board. Two experts weigh in: Sonali Raut, a senior data scientist at Munich RE Automation Solutions, and Alex Estevam, a technical program manager at Mastercard.

Cynthia is a newly hired software developer at MainFrame, which uses Scrum to manage projects. But she agrees with her coworkers that the company's methodical and deliberate pace is inferior to the quicker, more loosely structured approach of her previous employer, which used Flow. So when a colleague approaches her and asks her to use her impressive background and credentials to advocate for Flow, Cynthia agrees. But after her pilot project produces mixed results, she wonders whether she should proceed with a presentation to the process-improvement board. Two experts weigh in: Sonali Raut, a senior data scientist at Munich RE Automation Solutions, and Alex Estevam, a technical program manager at Mastercard.

Cynthia is a newly hired software developer at MainFrame, which uses Scrum to manage projects. But she agrees with her coworkers that the company's methodical and deliberate pace is inferior to the quicker, more loosely structured approach of her previous employer, which used Flow. So when a colleague approaches her and asks her to use her impressive background and credentials to advocate for Flow, Cynthia agrees. But after her pilot project produces mixed results, she wonders whether she should proceed with a presentation to the process-improvement board. Two experts weigh in: Sonali Raut, a senior data scientist at Munich RE Automation Solutions, and Alex Estevam, a technical program manager at Mastercard.

In February 2017 the Team Project Manager and Flow Project Coordinator for Dell Technologies-Limerick (Ireland), is preparing for a review with Dell's Systems and Processes Improvement board, early in a transition from the use of one agile software development method (Scrum) to another (Flow, which applies lean manufacturing techniques to software engineering). The new manager has been on board less than six months. With ten years' prior software development experience in Brazil, he moved to Ireland when hired by Dell. Dell is midway through its attempts to transform from a manufacturing-heavy strategy to an IT-supported service-heavy strategy; its recent acquisition of EMC is an important step in that direction, and executives expect Flow will help globally-distributed software developers produce higher quality code, faster, in follow-the-sun mode. The Flow coordinator/champion recognizes Flow is a complex innovation; it will take time and focus for busy software developers (who only recently mastered Scrum techniques) to master new Flow techniques. The champion is also concerned that needed digital Kanban functionality (essential for supporting globally distributed teams using Flow) has not yet been approved or provided by the Dell IT organization in Texas; this and other obstacles are impeding the developers' transition to Flow. Keen to demonstrate his commitment to help Dell achieve these aims, he worries that some executives expect performance improvements sooner than teams can realistically deliver. He seeks to persuade executives to be both patient and helpful. As he plans his 20 minute presentation for the next day's meeting, he is told to keep his remarks to executives simple: highlight no more than three messages.