160 likes | 281 Vues
The isolation of systems design from project management in current SDLC practices has contributed to the stagnation of IT governance and project failures over the decades. Notably, 44% of technology projects are only partially successful, indicating a need for integrated design processes. This approach emphasizes the importance of involving all stakeholders in understanding both the what and the how of project requirements, enabling iterative cost-benefit evaluations. By adopting a unified framework for systems and project planning, organizations can significantly improve project outcomes and overall governance quality.
E N D
Systems Planning and Project Planning: Is Integration Needed? One of the weaknesses in our current SDLC methodologies is the isolation of system design and project management practice Paul H. Rosenthal California State University, Los Angeles
The Poor Status of IT Governance I. Low Usage of Experienced Designers Project Failure reasons stable for 50 years II. Need for Integrated Design • 44% of technology projects are PARTIAL Successes • Our Status Score: C- • The Integration of system design and project management practice can help solve this problem The Standish Group Report
Quality of our Systems and Project Planning * Our Professional level Project Planning is not this Bad
1- Logical systems analysis (Initiation - find the underlying problem)
My Take on the Underlying Problems • Simplistic Physical Design • Typical charting methods do not present true scope and complexity of the systems • All stakeholders do not understand both WHAT and HOW • Lack of Design/Cost-Benefit Iteration • Management, technical, staffing , and financial participants in design cannot properly participate in the iterative cost-benefit process
The Physical Design Methodology For TPS, a physical design is created from a DFD based logical design, by separating processes and data stores by: time (daily vs. monthly, day vs. night ...), place (client or server, centralized vs. distributed...), online vs. batch, manual vs. automated, etc.