Project managers can learn as much, if not more, from failed projects as they can from successful ones. An infamous failed project is the Stretch project initiated in 1956 by a group of computer scientists at IBM who wanted to build the world’s fastest supercomputer. The result of this five-year project was the IBM 7030, also known as Stretch. It was the company’s first transistorized supercomputer. Though Stretch could handle a half-million instructions per second and was the fastest computer in the world up to 1964, the project was deemed a failure. Why? The project’s goal was to create a computer 100 times faster than what it was built to replace. Stretch was only about 30-40 times faster. The planned cost was $13.5 million, but the price dropped to $7.8 million; so, the computer was at least completed below cost. Only nine supercomputers were built. Research the Stretch project and the lessons learned. How would you have managed the Scope, Quality, and Time constraints as a project manager on the project to maintain the balance? In your response post, comment on whether you agree or disagree with your classmates. Support your comments with relevant references. Assignment create 2 response posts and a summary post on all discussion posts for this week Response Posts (at least two; each 75 - 100 words) and Summary Post 200 words: Due Tuesday @ 11:59 pm Discussion post Alex Julien IBM 7030, also known as the Stretch project, was initiated to support government laboratories participating in nuclear weapons research with a five-year goal to produce a supercomputer 100 times faster than the system it was supposed to replace in 1964. Unfortunately, the system created was only 30 to 40 times faster and therefore deemed a failure, but the research contributed positively to the computer industry and upcoming IBM products (The IBM 7030, aka Stretch). It should be noted that the supercomputer was supposed to cost $13.5 million but since expectations were not met the cost decreased to $7.8 million with the company losing a significant about of money. Considering only nine supercomputers were built, there are many factors to be considered when it comes to managing a complex project like the IBM 7030 Stretch. A delicate balance of scope, quality, and time constraints is required. A dynamic approach is necessary for achieving complex and ambitious goals. As a project manager I would start by re-evaluating the goal itself. Furthermore, considering scope prioritization, cross-functional communication, risk management, clear objectives with milestones, and a realistic timeline that considers delays and uncertainties. A process that allows for pivoting and reassessment periodically and when necessary is important as well. References: The IBM 7030, aka Stretch. IBM. (n.d.). https://www.ibm.com/history/stretch Nadia Moorehead Managing the Scope, Quality, and Time constraints as a project manager is one of the most crucial steps for the success of any project. When considering Scope management, one of the biggest challenges was the overly ambitious goal of creating the computer to be 100 times faster than existing computers. It was unrealistic due to the technology available at the time. To solve this, I would establish more realistic goals that would be achievable with the technology available. For example, setting a goal to be 40-50 times faster, would have been more attainable (Lock, 2020). When aiming for successful quality management, it is crucial to focus on the development of the technology as well as the testing of components to ensure quality. This will allow for adjustments and improvements early in the development phase based on the feedback received from the comprehensive testing process. I would also establish quality assurance checks. This will involve regular audits and reviews. Managing the project timeline to avoid delays and ensure timely completion of the project is an additional issue that needs to be addressed. To avoid the delays, I would develop a detailed project with a clear timeline. I would also break the project into smaller phases with their own deadlines. This approach will allow for better time management and allocation of resources. Some of the lessons learned include being sure to set realistic goals, ensuring thorough development and testing, being open to flexibility and adaptability, as well as keeping constant with regular communication and reviews. (Project Management Institute, 2017; Lock, 2020) References PMBOK® Guide: Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide). 6th Edition. Project Management Institute. Lock, D. (2020). Project Management. 11th Edition. Routledge. Jennisha Joseph Even though the Stretch project was deemed a failure at the time, it created a lasting legacy because a lot of effort that went into that project became very helpful to the rest of the computer industry. The stretch was a part of the IBM family which was the single most profitable and successful family of computers of all times. The stretch pioneered many computer features like pipelining which lines up instructions in a cue so that the computer does not have to wait between operations. Multiprogramming which enables a computer to juggle more than one program at a time, and memory protection which prevents unwanted memory access. Lessons Learned The mistakes from the stretch project provided valuable insights for future computer projects. To be a successful project leader continuous improvement and process optimization is crucial. By utilizing the past experiences from the stretch project leaders were able to make more informed decisions and navigate challenges effectively to create better computers and programs. Knowledge is power and by sharing information they were able to create a culture of learning. The lessons learned from the Stretch project paved the way for the development of new computer systems that are very successful today. Britteny Petersen The IBM Stretch project is a classic example of how project management can benefit from failures as much as from successes. The project's ambitious goal to create a supercomputer 100 times faster than its predecessor led to challenges in managing scope, quality, and time constraints. As a project manager, addressing these constraints while maintaining balance would require careful planning, realistic goal-setting, and ongoing risk assessment. Firstly, the scope of the project was overly ambitious, aiming for a performance increase of 100 times. This goal should have been critically evaluated and adjusted to a more achievable target, possibly aiming for a 50-60 times improvement, which might have led to a more successful outcome. Continuous scope management would involve regular reviews and adjustments based on progress and technological capabilities. Secondly, quality management in the Stretch project needed more emphasis on meeting realistic performance expectations. While the Stretch was indeed the fastest computer of its time, the failure to meet the 100x speed goal overshadowed this achievement. As a project manager, I would have ensured that the project’s quality benchmarks were aligned with achievable performance targets and industry standards, avoiding the mismatch between expectations and outcomes. Finally, the time constraint was another critical aspect. The five-year timeline was ambitious for such groundbreaking technology. As a project manager, I would have implemented incremental milestones, allowing for periodic reassessment of progress and adjustment of timelines as necessary. This approach would help in mitigating risks and managing stakeholder expectations effectively. In conclusion, the IBM Stretch project illustrates the importance of balanced project management. By setting realistic goals, aligning quality standards with achievable outcomes, and managing time effectively, a project manager can better navigate the challenges that arise, turning potential failures into valuable learning experiences. Reference: Schneck, P.B. (1987). The IBM 7030: Stretch. In: Supercomputer Architecture. The Kluwer International Series in Engineering and Computer Science, vol 31. Springer, Boston, MA. https://doi.org/10.1007/978-1-4615-7957-1_2 Tatianna Khadoo Despite being the company's first transistorized supercomputer and being completed on schedule and within budget, IBM's Stretch project, which was started in the 1950s with the goal of creating "the world's fastest supercomputer," was ultimately deemed a failure because it was only 30–40 times faster than its predecessor rather than 100 times faster, which was its main objective. All projects are based on four essential trade-offs: scope, quality, and time, as the IBM case illustrates. Establishing Realistic Goals: The project's original ambition, to run at 100 times the speed of current technology, was unduly aggressive. Establish goals only once you have a clear strategy in place to reach them. Verify the realism of your goal. Don't deceive yourself into believing that you can achieve unattainable objectives that are beyond the current capabilities of technology and human ability on a global scale. Scope Management: After examining the project, it is evident that the work's scope was either poorly specified, poorly managed, or both. The gap between planned and achieved performance is indicative of unrealistic expectations on the part of the project management. Cost Control and Budget: Although the project was completed under budget, it did not achieve the anticipated performance goals. Although cost containment is vital, it shouldn't come at the expense of project goals not met. Realities vs. Expectations: Although the project succeeded in supplying a new supercomputer for the basement, this did not satisfy all the players. Its performance was simply not up to par with what was advertised. Avoid making unfulfilled promises. Taking Care of Time, Quality, and Scope Limitations. I would handle the main limitations as follows if I oversaw the Stretch project. Scope Management: Clearly identify your goals while applying Moore's Law. Your goals should be to make concrete, quantifiable, and practical improvements using current technologies within constrained timeframes. Why, roughly 100 times? Establish each milestone as a manageable extension from the prior timeframe if every new silicon generation appears to double performance. Reassess the project scope on a regular basis and make any revisions. This would entail revisiting the project objectives considering fresh advancements in technology and real-world constraints. Communication with Stakeholders: Inform all relevant parties of scope modifications and reasonable results. It is possible to avoid scope creep and misalignment by controlling expectations and maintaining transparency. Managing Quality: Establish Measurable Criteria for Quality: The quality requirements ought to be attainable within the clearly defined restrictions of capacity and money. Again, this is a clear idea. Testing and validating the specification incrementally is recommended. This should be done before, during, and after each project delivery. This aids in identifying problems fast so that the group can make the necessary corrections. Core criteria: pay attention to the most important functional needs. Avoid doing things "just in time." Provide the functional specifications for the project's principal and highest-value output. Formulate a Practical Timetable: Create a thorough project timetable with reasonable completion dates. This covers all lag periods resulting from obstacles or delays. Oversee Development: Create a procedure for routine reviews whereby the project's progress is evaluated in relation to the schedule, and adjust schedules as needed based on the actual state of completion. Establish a dynamic monitoring system to track project progress. Handle Dependencies: Throughout the day, keep an eye on the status of all the dependencies that are connected to your planning by first identifying them all. Plan to promptly address any bottlenecks found here to avoid project delays. Therefore, the Stretch project offers valuable insights into managing large-scale technology projects in general. These include setting reasonable expectations for the project's required functions and anticipated delays, controlling the scope to maintain project viability, establishing reasonable quality standards and controls, and maintaining strict timekeeping to balance constraints and raise the likelihood of successful projects. Improving project management techniques requires being both modest and critical of both successes and mistakes. We do, after all, gain knowledge from both our failures and our victories. Dakarai Potter Discussion 1.1 The IBM Stretch project aimed to develop a supercomputer 100 times faster than existing models, but it ultimately fell short of its ambitious goals, leading to scope creep, delays, and unmet quality expectations. The key lessons learned include the importance of setting realistic goals, managing scope tightly, balancing quality with achievable targets, and maintaining effective time management and stakeholder communication. 1. Scope Management: - Set Clear, Achievable Goals: Instead of setting a goal of 100 times the speed, I would have set incremental milestones. For example, aiming first for 10 times faster, then 50 times, and finally 100 times faster as a stretch goal. 2. Quality Management: - Define Quality Metrics Early: Quality standards should be clearly defined from the outset, with measurable metrics that can be tracked throughout the project. These metrics would focus on performance, reliability, and user satisfaction. 3. Time Management: - Realistic Scheduling: Develop a project schedule that accounts for potential delays and uncertainties, particularly those related to technological development. A phased approach with buffer times built in would help manage unexpected challenges. As a project manager, I would have set more achievable goals, implemented strict scope control, defined clear quality metrics, and created a realistic schedule with regular progress reviews. Balancing these constraints requires continuous monitoring and flexibility to ensure the project remains on track and delivers value. Maintaining balance between scope, quality, and time involves continuous monitoring and adjustment. A flexible approach that allows for incremental progress, coupled with strong yet flexible management and stakeholder communication, would help ensure that the project remains viable and delivers value, even if the initial ambitious goals need to be adjusted.
READ MORE >>
