Please enable JavaScript.
Coggle requires JavaScript to display documents.
Atek Case Study - Coggle Diagram
Atek Case Study
Timeline
- Recognized need to adapt to market, John Strider, CIO for Atek, approves Project Management Office (PMO) to handle changes.
- 2006, established strategic planning office to work with PMO in managing changes.
- 2000s, less demand for PCs due to PDAs, mobile phones and web apps.
- Atek hired experienced project management professionals
-
- 1990s, rapid growth in PC industry
- 2007, IT project were typically managed by allocating PM responsibilities to lead analysts (Linda Star)
This informal "order taker" method was great at first in communication, building trust, and meeting business needs.
Until IT was needed to focus on completing the project, rather than hashing out the requirements and taking the order.
1.1984, Atek became a mid-sized, U.S pc maker
- Project became more complex and needed more than a single work group. Informal system could no longer support complex project.
9.PMOs purpose, responsibilities, and authority unclear; duties divided into two categories
Project Focused: consulting, mentoring and training. Used to prove the merits of the PMO.
Enterprise-Oriented: portfolio management, PM standards, methods, tools, and project performance archives.
- Organizational models are considered. PMO-heavy and PMO-light.
- PMOs continue to work to be accepted others within the organization and adapt to the culture.
Relevant Facts
-
challenging to get the IT department to start using formal project management appproaches due to them not knowing the software and methododlogies
-
-
-
-
-
-
Key Problems
Cultural Resistance
Many employees view project management as administrative overhead and prefer the informality of their practices.
-
-
-
-
Lack of experience with formal project management and refusal to adopt new processes will challenge to PMO implementation.
-
-
-