Talk:Project management

From Wikipedia, the free encyclopedia
Jump to: navigation, search


I think the pre-WWII stuff should be deleted, as it is primarily "legitimizing myth" -- project management as a distinct discipline with distinct tools did not exist before World War II. Jonahc (talk) 05:48, 11 July 2016 (PST)

Good idea as to improving readability of this article, but as someone who writes in the area of engineering history I am interested in the Pre WWII era management practices. I agree with you but they were PMs then in terms of managing projects using proto-PM tools and they did work on developing those tools and practices, it just wasn't recognized as a separate discipline with formal history. Therefore, I would recommend moving that material into a separate article using verifiable sources.
BTW:I also agree with your comments on "myth building" which is why I work with published sources. I had an acquaintance who wrote a dissertation on the development of network scheduling, that was an exercise in cutting through the self-promotion and myth-building. It is important to reveal the history in the discipline. Many thanks ... Risk Engineer (talk) 13:56, 8 October 2016 (UTC)

Portal Layout[edit]

Can we convert this topic into a portal type setup similar to either the wikipedia portal or something like agriculture? It just seems there are so many details within this topic that being able to look up "project management" and having direct access to materials specific in the PMBOK and other methodologies makes sense. Perhaps having link sections on project management maths and formulas, section for the ITTOs and management styles etc etc.

I think this would be immeasurably helpful to people who need to look up this information. I'd help it all together if the request is approved.

Thanks, Scot

--scot.mcpherson (talk) 10:07, 6 February 2012 (CST)

Agile project management[edit]

this statement "It is the only technique in which the client will be actively involved in the project development." is total nonsense and should be removed or re-written such as "In Agile the client will be actively involved in the project development." — Preceding unsigned comment added by Ktlonergan (talkcontribs) 10:43, 25 December 2015 (UTC)

External links modified[edit]

Hello fellow Wikipedians,

I have just modified one external link on Project management. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

You may set the |checked=, on this template, to true or failed to let other editors know you reviewed the change. If you find any errors, please use the tools below to fix them or call an editor by setting |needhelp= to your help request.

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

If you are unable to use these tools, you may set |needhelp=<your help request> on this template to request help from an experienced user. Please include details about your problem, to help other editors.

Cheers.—cyberbot IITalk to my owner:Online 08:24, 2 April 2016 (UTC)

unsourced agile section[edit]

the following is unsourced and "truthy" - moving here until this can be reliably sourced

Agile project management
The iteration cycle in agile project management

Agile project management encompasses several iterative approaches based on the principles of human interaction management and founded on a process view of human collaboration. This sharply contrasts with traditional approaches such as the Waterfall method. In agile software development or flexible product development, the project is seen as a series of relatively small tasks conceived and executed to conclusion as the situation demands in an adaptive manner, rather than as a completely pre-planned process.

Advocates of this technique claim that:

  • It is the most consistent project management technique since it involves frequent testing of the project under development.
  • It is the only technique in which the client will be actively involved in the project development.
  • The only disadvantage with this technique is that it should be used only if the client has enough time to be actively involved in the project.

Agile is an umbrella term for multiple project management methodologies, including:

  • Scrum - A holistic approach to development that focuses on iterative goals set by the Product Owner through a backlog, which is developed by the Delivery Team through the facilitation of the Scrum Master.
  • Extreme Programming (XP) - A set of practices based on a set of principles and values, with a goal to develop that provides real value by implementing tight feedback loops at all levels of the development process and using them to steer development. XP popularized Test Driven Development (TDD) and Pair Programming.
  • eXtreme Manufacturing (XM) - An agile methodology based on Scrum, Kanban and Kaizen that facilitates rapid engineering and prototyping.
  • Crystal Clear - An agile or lightweight methodology that focuses on colocation and osmotic communication.
  • Kanban (看板?) - A lean framework for process improvement that is frequently used to manage work in progress (WIP) within agile projects. Kanban has been specifically applied in software development.
  • Scrumban a mixed scrum and kanban approach to project management. It focuses on taking the flexibility of kanban and adding the structure of scrum to create a new way to manage projects.

-- Jytdog (talk) 19:37, 17 April 2016 (UTC)