Software product management

  • 292 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
292
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
14
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1.  DefinitionSoftware product management is the process ofmanaging software that is built and implemented asa product, taking into account life-cycleconsiderations and generally with a wide audience. Itis the discipline and business process which governs aproduct from its inception to the market or customerdelivery and service in order to generate biggestpossible value to the business
  • 2.  Aspects of software developmentA software development process isconcerned primarily with the productionaspect of software development, asopposed to the technical aspect, such assoftware tools. These processes existprimarily for supporting the management ofsoftware development, and are generallyskewed toward addressing businessconcerns. Many software developmentprocesses can be run in a similar way togeneral project management processes
  • 3.  Risk management Risk management is the process of measuring or assessing risk and then developing strategies to manage the risk. In general, the strategies employed include transferring the risk to another party, avoiding the risk, reducing the negative effect of the risk, and accepting some or all of the consequences of a particular risk. Risk management in software project management begins with the business case for starting the project, which includes a cost-benefit analysis as well as a list of fallback options for project failure, called a contingency plan
  • 4.  Requirements managementRequirements management is the process ofidentifying, eliciting, documenting, analyzing,tracing, prioritizing and agreeing on requirementsand then controlling change and communicating torelevant stakeholders. New or altered computersystem Requirements management, which includesRequirements analysis, is an important part of thesoftware engineering process; whereby businessanalysts or software developers identify the needsor requirements of a client; having identified theserequirements they are then in a position to design asolution.
  • 5.  Change managementChange management is the process ofidentifying, documenting, analyzing, prioritizingand agreeing on changes to scope (projectmanagement) and then controlling changes andcommunicating to relevant stakeholders.Change impact analysis of new or altered scope, which includes Requirementsanalysis at the change level, is an important part of the software engineeringprocess; whereby business analysts or software developers identify the alteredneeds or requirements of a client; having identified these requirements they arethen in a position to re-design or modify a solution. Theoretically, each changecan impact the timeline and budget of a software project, and therefore bydefinition must include risk-benefit analysis before approval.
  • 6.  Software configuration management Software configuration management is the process of identifying, and documenting the scope itself, which is the software product underway, including all sub-products and changes and enabling communication of these to relevant stakeholders. In general, the processes employed include version control, naming convention (programming), and software archival agreements.
  • 7.  Release managementRelease management is the process of identifying,documenting, prioritizing and agreeing on releasesof software and then controlling the releaseschedule and communicating to relevantstakeholders.Most software projects have access to three software environments towhich software can be released; Development, Test, and Production. Invery large projects, where distributed teams need to integrate their workbefore release to users, there will often be more environments for testing,called unit testing, system testing, or integration testing, before release toUser acceptance testing (UAT).
  • 8. The purpose of project planning is to identifythe scope of the project, estimate the workinvolved, and create a project schedule.Project planning begins with requirementsthat define the software to be developed. Theproject plan is then developed to describe thetasks that will lead to completion.The purpose of project monitoring and control is to keep the team andmanagement up to date on the projects progress. If the project deviatesfrom the plan, then the project manager can take action to correct theproblem. Project monitoring and control involves status meetings to gatherstatus from the team. When changes need to be made, change control isused to keep the products up to date.
  • 9. Project management software industrys futurelooks especially promising. During the global recession,industrial countries around the world devoted billions ineconomic stimulus funds for infrastructure and otherprojects. This has created considerable demand for projectmanagement software.
  • 10. HR Software – Building Robust Management Solutions For The Future - By AmitBhagriahttp://www.merl.com/areas/bpm/http://bcalliance-international.com/our-services/risk-managementhttp://blogs.msdn.com/b/willy-peter_schaub/archive/2011/01/13/requirements-management-guidance-where-is-the-feature-work-item-type.aspxhttp://findicons.comhttp://www.turbosquid.com/3d-models/conveyor-belts-max/369307http://techchai.com/2011/07/07/free-project-planning-software-to-improve-your-daily-work/http://iamhash.blogspot.com/2011/06/anatomy-of-success.htmlhttp://en.wikipedia.org/wiki/Software_project_managementThe Future of IT Project Management Software - By Stacy A. Goff