In Poor Richard’s Almanac, Benjamin Franklin penned the familiar lines: “For the want of a nail the shoe was lost, for the want of a shoe the horse was lost, for the want of a horse the rider was lost, for the want of a rider the battle was lost, for the want of a battle the kingdom was lost—and all for the want of a horseshoe nail.” Looking at the outcome in hindsight, could project management concepts have avoided the loss of the kingdom? How?

In Poor Richard’s Almanac, Benjamin Franklin penned the familiar lines: “For the want of a nail the shoe was lost, for the want of a shoe the horse was lost, for the want of a horse the rider was lost, for the want of a rider the battle was lost, for the want of a battle the kingdom was lost—and all for the want of a horseshoe nail.” Looking at the outcome in hindsight, could project management concepts have avoided the loss of the kingdom? How?

Information Technology Project Management

9th Edition

ISBN:9781337101356

Author:Kathy Schwalbe

Publisher:Kathy Schwalbe

Chapter4: Project Integration Management

Section: Chapter Questions

Problem 1E: Write a short paper based on the chapters opening case. Answer the following questions: a. What do...

See similar textbooks

Similar questions

Write a short paper based on the chapters opening case. Answer the following questions: a. What do you think the real problem was in this case? b. Does the case present a realistic scenario? Why or why not? c. Was Nick Carson a good project manager? Why or why not? d. What should top management have done to help Nick? e. What could Nick have done to be a better project manager?
Have you ever used a top-down approach to design in your work? If so, please inform us. If you replied affirmatively, please clarify what you mean. Create a paper discussing at least one instance of top-down design and how it aids a project management team in completing the objective.
Have you used top-down design principles before? If so, in what context. Write about at least one example of top-down design and how it makes a project manageable for a team.
In their paper, Andersen et al (2006) stated that the basic idea behind the traditional, rational and normative project approach is that projects are relatively simple, predictable and linear with clearlydefined boundaries which all makes it easy to plan in detail and follow that plan without much changes. On the other hand, Agile project management approach is intended for projects characterized by high level of uncertainty, unclear project goals or incomplete and unpredictable requests, for which it could be assumed that will be significantly changed during the course of the project .With reference to the statement and scenario above, Motivate why a mixed methodology (Agileand Traditional Methodology) is most ideal for this project. In your answer, ensure that you address what was established in the meeting.
Discuss the main metrics for static testing and Path testing, and show how static testing and Path testing save project managers money by justifying it in terms of savings to cost ratio.
For project managers, metrics for static testing and route testing are crucial, and a detailed discussion of these metrics may help the managers save money.
This high-level initial estimate of the requirements is maintained by the Project Owner throughout the entire project. It is dynamic because management can constantly change it to reflect the needs of an evolving product, and its environment. a. A Timebox b. A Product Backlog c. An Iteration d. A Sprint Backlog
Consider a project and map it both with and without architecture.What effect it will have on the finished product