QSO 435 Milestone Two Guidelines and Rubric

Scenario Selection: Dell Technologies Flow Transition.

Dell Technologies-Limerick is transitioning its software development approach from Scrum to Flow, a lean system that will support a new service-focused business strategy. Under the leadership of Flow Coordinator Larry Ferreira, the program involves 36 developers working in teams around the globe in a follow-the-sun approach to curb the high rate of hardware obsolescence and intense competition. The initial statistics presented by Team 1 indicate positive progress: average lead times have reduced to 39 days, and cycle times have dropped to 24 days. Nevertheless, the project has major requirements, including the need for computerized Kanban tools to replace manual data collection (Alam and Priti,2024). Success presupposes that the organization can address the cultural issues and technical constraints of its code management software to present data to the Systems and Process Improvement (SPI) Board on the quality of its high-speed deliveries.

Comparison of TPM and APM: Concepts and Parties.

In both the past and the present, Dell has used Traditional Project Management (TPM) and Adaptive Project Management (APM). TPM is defined as a Waterfall discipline in which projects are designed in stringent, step-wise stages with extensive documentation at the beginning of the plan, possibly managed by top directors such as Mark Fitzpatrick, who focus on stable, long-term roadmaps. On the other hand, APM methods such as Scrum and Flow focus on iterative discovery and on responding to change rather than strict adherence to a plan. The important stakeholders in this changing environment are Product Owner Amélie Berger, who facilitates user requirements through so-called themes and epics, and the developers, who now have to learn new tools such as Value Stream Mapping. For example, Dell APM is based on the principle of daily standups, where team members report their progress to each other, fostering a culture of instant transparency and active learning.

Triple Constraint of the Traditional Project Management.

The triple constraint (scope, time, and cost) in the TPM model previously applied at Dell is treated as a fixed triangle, where any change in one element usually forces a compromise on the other two. The requirements (scope) are then defined and formalised through structured models such as data flow diagrams, and coding (time) does not start until coding begins. The result of this strategy is usually a two- or three-year project deadline, during which the completed software may no longer meet current business requirements due to the rapid pace of the technology market (Susarla,2026). When the scope of projects increases during these long cycles, it is bound to either cost more or lead to significant delays. Therefore, the strict management of these constraints within Waterfall is usually prone to poor performance or delays that cannot keep up with the rapidly evolving software provided by Dell.

Project Management Approaches Review.

Dell employs various project management models, such as Waterfall, Scrum, Flow, and Hybrid, to accommodate project complexities. In contrast to Waterfall, which provides a strict approach to defining products, Scrum proposes time-limited sprints and velocity indicators to enable more frequent software deliveries. Flow also streamlines the process by abandoning batches in favor of single-piece flow, which is more concerned with processing queues and reducing waste than with following project timelines. A Hybrid approach combining Waterfall's strong preliminary definition with Agile's regular two-week release cycles is used effectively by some Dell teams. These different approaches enable the PMO to strike the right balance between early planning and the flexibility necessary to deliver software continuously and efficiently in a global setting.

References

Alam, M. M., & Priti, S. I. (2024).  Adaptive Hybrid Software Project Management in Bangladesh’s Software Industry: Navigating the Cultural Transformation and Ensuring On-Time Delivery (Doctoral dissertation, IUB).

Susarla, R. S. (2026, February). Assessing Agile Frameworks for Software Development Efficiency Industry Insights and Implementation with Jira Atlassian Agile Tools. In  2026 IEEE 5th International Conference on AI in Cybersecurity (ICAIC) (pp. 1-6). IEEE.