![]() | This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||
|
I am working on rewriting and merging "Software project management" and "Project Management Software". Any feedback or suggestions would be appreciated. My current plan is to merge both pages into "Project Management Software"; thoughts? PMDude ( talk) 04:19, 1 December 2009 (UTC)
This page is really pitiful.
Any knowledgeable people want to attempt a rewrite?
I'm taking a slow careful stab at it. Are there any layout examples anyone wants to recommend? -- April 27, 2023 - Rich Legge — Preceding unsigned comment added by Richlegge ( talk • contribs) 21:51, 27 April 2023 (UTC)
The last edit added a section on Open Source tools with no content... should this be removed? -- HobbesLeviathan ( talk) 01:41, 12 April 2008 (UTC)
I just came across this page. Will try to find some scholarly stuff and edit it but will take time. Affan Laghari ( talk) 13:52, 2 July 2008 (UTC)
There is a move discussion in progress on Template talk:IEEE software documents which affects this page. Please participate on that page and not in this talk page section. Thank you. — RMCD bot 22:02, 15 June 2020 (UTC)
This article is quite old. Should I edit this page and replace with modern content or write a new page/article. Richlegge ( talk) 00:54, 28 April 2023 (UTC)
Since software development process has its own page, doesn't it make more sense to limit all the text related specifically to development in this page? It would seem to better serve the community to leave all the software development topics to those numerous pages.
Software Project Management is not "a process". A process is repetative, software project management is a unique activity for each project with a defined end, it is not "never ending" like a process is. Richlegge ( talk) 15:53, 28 April 2023 (UTC)
If PMI a govering body of software project management, can an internal link to the PMBOK and PMI Wikipage be edited in. The software project management page links to nearly everything else, why not PMBOK and PMI? Richlegge ( talk) 16:54, 1 May 2023 (UTC)
Software project management is the practice/discipline of managing a software project through multiple overlapping phases starting with conception/initiation and continuing through subsequent phases of planning, execution, monitoring, completion and close down.
Standards organizations such as International Organization of Standards (ISO), Open Geospatial Consortium (OGC), National Institute of Standards and Technology (NIST), Institute of Electrical and Electronics Engineers (IEEE), Software Engineering Institute (SEI), Project Management Institute (PMI) and others all provide definitions for Software Project Management. These definitions are used by organizations all over the world in their attempts to successfully deliver a set of software features to an identified customer.
<-- See Also section to have internal links to each of the above mentioned organizations --> Richlegge ( talk) 21:14, 1 May 2023 (UTC)
Shouldn't some of the topics such as software bugs be moved over to software development article? Bugs and testing specific "issues" would seem to belong in software development article because they are "issues" specific to the software development team and are not the more general type of project level issues.
Below is the topic lead for software development:
Software development is the process of conceiving, specifying, designing, programming, documenting, testing, and bug fixing involved in creating and maintaining applications, frameworks, or other software components. Software development involves writing and maintaining the source code, but in a broader sense, it includes all processes from the conception of the desired software through the final manifestation, typically in a planned and structured process often overlapping with software engineering. Software development also includes research, new development, prototyping, modification, reuse, re-engineering, maintenance, or any other activities that result in software products.[1]
The project related "issue" are items such as costs, schedule, scope, communications, etc.... and are generally not software development specific. Typically, development team issues, or bugs, are not brought up at the project level.
-- Richlegge ( talk) 20:56, 2 May 2023 (UTC)
Why is the IEEE Life Cycle referenced here, wouldn't it more apporopriately belong to Software development process ?
-- Richlegge ( talk) 22:11, 3 May 2023 (UTC)
In searching this page there is zero references to project closure. If software project management is a sub-set of project management, then doesn't it logically follow that project closure should be mentioned on this page or is there some resistence or reluctance?
"Project Management is the process of guiding a project from it beginning through its performance to its closure."
-- Book=Project Management for Dummies, 2nd Edition -- Published by Wiley Publishing -- Copyright 2007
-- Richlegge ( talk) 22:26, 3 May 2023 (UTC)
Suggested New Lead taken from Software Extension to the PMBOK® Guide – Fifth Edition
** Remember, this document is joint effort between PMI and IEEE.
In addition to creating new products, software projects are often undertaken to modify an existing software product,to integrate a set of existing software components, or to modify the software infrastructure of an organization. Software projects may also be undertaken to satisfy service requests, maintenance needs, and to provide operations support; however these activities may occur as low-level continuous activities; they are considered projects only when they are specified as: temporary endeavors that occur within predetermined timeframes to provide deliverables and outcomes.
I guess the question needs to be decided is if the desired subject of this page to be about Software Engineering Management or Software Project Management? It seems Software Engineering Management is the domain of IEEE and Software Project management is domain of PMI. It seems this is by mutual agreement of those organizations.
--- Rich Legge Richlegge ( talk) 19:27, 19 May 2023 (UTC)
![]() | This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||
|
I am working on rewriting and merging "Software project management" and "Project Management Software". Any feedback or suggestions would be appreciated. My current plan is to merge both pages into "Project Management Software"; thoughts? PMDude ( talk) 04:19, 1 December 2009 (UTC)
This page is really pitiful.
Any knowledgeable people want to attempt a rewrite?
I'm taking a slow careful stab at it. Are there any layout examples anyone wants to recommend? -- April 27, 2023 - Rich Legge — Preceding unsigned comment added by Richlegge ( talk • contribs) 21:51, 27 April 2023 (UTC)
The last edit added a section on Open Source tools with no content... should this be removed? -- HobbesLeviathan ( talk) 01:41, 12 April 2008 (UTC)
I just came across this page. Will try to find some scholarly stuff and edit it but will take time. Affan Laghari ( talk) 13:52, 2 July 2008 (UTC)
There is a move discussion in progress on Template talk:IEEE software documents which affects this page. Please participate on that page and not in this talk page section. Thank you. — RMCD bot 22:02, 15 June 2020 (UTC)
This article is quite old. Should I edit this page and replace with modern content or write a new page/article. Richlegge ( talk) 00:54, 28 April 2023 (UTC)
Since software development process has its own page, doesn't it make more sense to limit all the text related specifically to development in this page? It would seem to better serve the community to leave all the software development topics to those numerous pages.
Software Project Management is not "a process". A process is repetative, software project management is a unique activity for each project with a defined end, it is not "never ending" like a process is. Richlegge ( talk) 15:53, 28 April 2023 (UTC)
If PMI a govering body of software project management, can an internal link to the PMBOK and PMI Wikipage be edited in. The software project management page links to nearly everything else, why not PMBOK and PMI? Richlegge ( talk) 16:54, 1 May 2023 (UTC)
Software project management is the practice/discipline of managing a software project through multiple overlapping phases starting with conception/initiation and continuing through subsequent phases of planning, execution, monitoring, completion and close down.
Standards organizations such as International Organization of Standards (ISO), Open Geospatial Consortium (OGC), National Institute of Standards and Technology (NIST), Institute of Electrical and Electronics Engineers (IEEE), Software Engineering Institute (SEI), Project Management Institute (PMI) and others all provide definitions for Software Project Management. These definitions are used by organizations all over the world in their attempts to successfully deliver a set of software features to an identified customer.
<-- See Also section to have internal links to each of the above mentioned organizations --> Richlegge ( talk) 21:14, 1 May 2023 (UTC)
Shouldn't some of the topics such as software bugs be moved over to software development article? Bugs and testing specific "issues" would seem to belong in software development article because they are "issues" specific to the software development team and are not the more general type of project level issues.
Below is the topic lead for software development:
Software development is the process of conceiving, specifying, designing, programming, documenting, testing, and bug fixing involved in creating and maintaining applications, frameworks, or other software components. Software development involves writing and maintaining the source code, but in a broader sense, it includes all processes from the conception of the desired software through the final manifestation, typically in a planned and structured process often overlapping with software engineering. Software development also includes research, new development, prototyping, modification, reuse, re-engineering, maintenance, or any other activities that result in software products.[1]
The project related "issue" are items such as costs, schedule, scope, communications, etc.... and are generally not software development specific. Typically, development team issues, or bugs, are not brought up at the project level.
-- Richlegge ( talk) 20:56, 2 May 2023 (UTC)
Why is the IEEE Life Cycle referenced here, wouldn't it more apporopriately belong to Software development process ?
-- Richlegge ( talk) 22:11, 3 May 2023 (UTC)
In searching this page there is zero references to project closure. If software project management is a sub-set of project management, then doesn't it logically follow that project closure should be mentioned on this page or is there some resistence or reluctance?
"Project Management is the process of guiding a project from it beginning through its performance to its closure."
-- Book=Project Management for Dummies, 2nd Edition -- Published by Wiley Publishing -- Copyright 2007
-- Richlegge ( talk) 22:26, 3 May 2023 (UTC)
Suggested New Lead taken from Software Extension to the PMBOK® Guide – Fifth Edition
** Remember, this document is joint effort between PMI and IEEE.
In addition to creating new products, software projects are often undertaken to modify an existing software product,to integrate a set of existing software components, or to modify the software infrastructure of an organization. Software projects may also be undertaken to satisfy service requests, maintenance needs, and to provide operations support; however these activities may occur as low-level continuous activities; they are considered projects only when they are specified as: temporary endeavors that occur within predetermined timeframes to provide deliverables and outcomes.
I guess the question needs to be decided is if the desired subject of this page to be about Software Engineering Management or Software Project Management? It seems Software Engineering Management is the domain of IEEE and Software Project management is domain of PMI. It seems this is by mutual agreement of those organizations.
--- Rich Legge Richlegge ( talk) 19:27, 19 May 2023 (UTC)