|WikiProject Systems||(Rated Start-class, High-importance)|
|WikiProject Technology||(Rated Start-class)|
improvements vs projects
Sir/Madam, Organisations tend to stretch the Project definition in the direction suitable for their particular arguments in a particular situation. Maybe it's not worth while to have a strict definition, but yet again- it creates confusion when we do not agree on what a project is and what it isn't. Some are using the term 'Improvement' when they talk about small projects, but what is a small project? It's an interesting discussion to try to find more common definition. Do you have any suggestions?
Tor Murvold Ms Science Chief PM
- How can you tell if it's a project? Well, if the outcome is something new (to you), and it requires a plan, people, time, and money to complete, then it's a project. The work required to make an improvement is a project. It doesn't matter if it's a 2-hour project (as seen in home improvement or hobbies) or a 2-year project. Ancawonka 01:03, 31 January 2006 (UTC)
Current list of examples seems biased towards the USA how about so -Building of the pyramids -Noah's Ark -Great wall of China (seriously though, did projects only start in the 20th century ? all of the above are certainly unique products !) -Channel Tunnel (UK-France) -Concorde (UK-France)
Do others agree list should be more balanced between historical and present / developed and developing countries ?
- Yes, why not? Ancawonka 01:03, 31 January 2006 (UTC)
There are several characteristics in a project.
Planning - Planning required in a project and it involves several phases.
Objective - Objective should be set in the early stage.
Scope - To identify which tasks to be covered in a project.
Time - pre-determined the time span to defines what tasks are to be undertaken at a time.
Resources - A set of resources can be used to meet the project objective, such as human, hardware, software, money.
Quality - A standard of a project should be stated clearly in an early phase.
Risk - Risk that might occurs in the development phase should be defines, and an intelligent way to resolve a problem.
The section titled 'Based on requisite process model' should probably be moved to a software oriented page such as Software Projects or perhaps a new page Software Project. Jongrover 17:21, 22 June 2007 (UTC)
== Headline text == the name of the topic is mentioned on top .#REDIRECT Target page name den the target will be set on which point include inthis target.
nedt step will be the no of topic —Preceding unsigned comment added by 22.214.171.124 (talk) 10:32, 12 March 2010 (UTC)
There's "projects" and then there's "projects"
In my totally "original research" experience, there are two definitions of "project" about, or two categories of definitions, and this article only covers one. The one covered can be called "finite extent, defined outcome" projects: the project to build this or that, for example. The other one is "unbounded evolution of persistent objects." I can only name examples of the latter type from the software development field: the Linux project, for example. In the latter definition, there's no definable termination--there are probably many finite/defined subgroups of work (that is, "projects" in the former sense), but they're called "releases." It seems like this article would be a great place to draw out this distinction. Can anyone provide citations for my latter usage? Jackrepenning (talk) 19:24, 23 March 2010 (UTC)
More OR - but the same thing happens in electronic product design projects, or probably any field where innovation is involved (even construction). The project can be iterative, or a bit more freeform, but can't be split easily into distinct design and build phases as the engineering project section suggests (although this remains an ideal). The functional requirements, and hence the design, may be unknown until the first units are manufactured (engineering samples for customers to try out). --Adx (talk) 23:41, 30 January 2013 (UTC)