Failure to address such issues can lead to poorly defined system requirements and other problems. Creating software brings other potential challenges as well, such as navigating through stakeholder politics and communicating clearly with end-users, developers, and others. Software development comes with multiple risks and challenges - frequent technology changes, immature technology, sloppy development practices, and staff and management turnover, to name a few. Software project management ensures that the project in question aligns with business goals, achieves high-quality results, and delivers real value to all stakeholders. Project managers have a big responsibility - one that involves much more than avoiding overdue, over-budget software projects. The already-popular project management practices were the perfect fit for managing the lifecycle of software projects. As the industry grew, software manufacturers required formalized practices for controlling and releasing software tools. In 1969, however, IBM began selling their software as a standalone product, thereby establishing an industry exclusively dedicated to software. Initially, companies packaged software as part of the purchase or lease of a computer. John Tukey, a Princeton University statistician, introduced the term “software” in 1958. You can find a concise history of project management methodologies here. Today, project management practices take place across organizations of all sizes and in all industries, including manufacturing, information technology (IT), marketing, finance, and construction. Project management dates back to the start of human civilization, but modern project management was born in the early part of the 20th century, when Henry Gantt developed the Gantt chart. The term software project management refers to the planning, scheduling, and organization of a software development project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |