Incorporating Learning and Expected Cost of Change in Prioritizing Features on Agile Projects
Very little has been written to date on how to prioritize and sequence the development of new features and capabilities on an agile software development project. Agile product managers have been advised to prioritize based on “business value.” While this seems an appropriate goal, it is vague and pr...
Gespeichert in:
| Hauptverfasser: | , |
|---|---|
| Format: | Tagungsbericht |
| Sprache: | eng |
| Schlagworte: | |
| Online-Zugang: | Volltext |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| container_end_page | 180 |
|---|---|
| container_issue | |
| container_start_page | 175 |
| container_title | |
| container_volume | |
| creator | Harris, R. Scott Cohn, Mike |
| description | Very little has been written to date on how to prioritize and sequence the development of new features and capabilities on an agile software development project. Agile product managers have been advised to prioritize based on “business value.” While this seems an appropriate goal, it is vague and provides little specific guidance. Our approach to optimizing “business value” uses tactics to minimize costs and maximize benefits through strategic learning. In order to provide specific and actionable advice to agile product managers, we present two guidelines. These guidelines are meant to provide a set of considerations and a process by which an agile product manager can achieve the goal of optimizing “business value” while recognizing that different product managers will vary in their notions of what “business value” is. |
| doi_str_mv | 10.1007/11774129_19 |
| format | Conference Proceeding |
| fullrecord | <record><control><sourceid>pascalfrancis_sprin</sourceid><recordid>TN_cdi_pascalfrancis_primary_19105369</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>19105369</sourcerecordid><originalsourceid>FETCH-LOGICAL-p219t-a6a37c8339655860e2c6ad614b45fad9b03df509d96dee1ef46ccca51f5893233</originalsourceid><addsrcrecordid>eNpNkE9LAzEQxeM_sNae_AK5ePCwmtlJss2xLK0KBT3oUZY0m62pNVmSFdRPb0oFncsbeG8G3o-QC2DXwFh1A1BVHErVgDogZyg4Q8GUYIdkBBKgQOTq6M_g5TEZMWRloSqOp2SS0oblQagkVCPycu9NiH2IenB-TZdWR79btG_p_LO3ZrAtrUMaaOho_ar92lLn6WN0IbrBfe-yC6uHj2gTDZ7O1m5rsx02-TSdk5NOb5Od_OqYPC_mT_VdsXy4va9ny6IvQQ2FlhorM0VUUoipZLY0UrcS-IqLTrdqxbDtcplWydZasB2XxhgtoBNThSXimFzu__Y6Gb3tovbGpaaP7l3Hr4wKmECpcu5qn0vZylViswrhLTXAmh3c5h9c_AFphmck</addsrcrecordid><sourcetype>Index Database</sourcetype><iscdi>true</iscdi><recordtype>conference_proceeding</recordtype></control><display><type>conference_proceeding</type><title>Incorporating Learning and Expected Cost of Change in Prioritizing Features on Agile Projects</title><source>Springer Books</source><creator>Harris, R. Scott ; Cohn, Mike</creator><contributor>Succi, Giancarlo ; Abrahamsson, Pekka ; Marchesi, Michele</contributor><creatorcontrib>Harris, R. Scott ; Cohn, Mike ; Succi, Giancarlo ; Abrahamsson, Pekka ; Marchesi, Michele</creatorcontrib><description>Very little has been written to date on how to prioritize and sequence the development of new features and capabilities on an agile software development project. Agile product managers have been advised to prioritize based on “business value.” While this seems an appropriate goal, it is vague and provides little specific guidance. Our approach to optimizing “business value” uses tactics to minimize costs and maximize benefits through strategic learning. In order to provide specific and actionable advice to agile product managers, we present two guidelines. These guidelines are meant to provide a set of considerations and a process by which an agile product manager can achieve the goal of optimizing “business value” while recognizing that different product managers will vary in their notions of what “business value” is.</description><identifier>ISSN: 0302-9743</identifier><identifier>ISBN: 3540350942</identifier><identifier>ISBN: 9783540350941</identifier><identifier>EISSN: 1611-3349</identifier><identifier>EISBN: 3540350950</identifier><identifier>EISBN: 9783540350958</identifier><identifier>DOI: 10.1007/11774129_19</identifier><language>eng</language><publisher>Berlin, Heidelberg: Springer Berlin Heidelberg</publisher><subject>Agile Software Development ; Analytic Hierarchy Process ; Applied sciences ; Computer science; control theory; systems ; Exact sciences and technology ; Product Manager ; Software ; Software engineering ; Strategic Learning ; User Story</subject><ispartof>Extreme Programming and Agile Processes in Software Engineering, 2006, p.175-180</ispartof><rights>Springer-Verlag Berlin Heidelberg 2006</rights><rights>2007 INIST-CNRS</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktopdf>$$Uhttps://link.springer.com/content/pdf/10.1007/11774129_19$$EPDF$$P50$$Gspringer$$H</linktopdf><linktohtml>$$Uhttps://link.springer.com/10.1007/11774129_19$$EHTML$$P50$$Gspringer$$H</linktohtml><link.rule.ids>309,310,779,780,784,789,790,793,4047,4048,27923,38253,41440,42509</link.rule.ids><backlink>$$Uhttp://pascal-francis.inist.fr/vibad/index.php?action=getRecordDetail&idt=19105369$$DView record in Pascal Francis$$Hfree_for_read</backlink></links><search><contributor>Succi, Giancarlo</contributor><contributor>Abrahamsson, Pekka</contributor><contributor>Marchesi, Michele</contributor><creatorcontrib>Harris, R. Scott</creatorcontrib><creatorcontrib>Cohn, Mike</creatorcontrib><title>Incorporating Learning and Expected Cost of Change in Prioritizing Features on Agile Projects</title><title>Extreme Programming and Agile Processes in Software Engineering</title><description>Very little has been written to date on how to prioritize and sequence the development of new features and capabilities on an agile software development project. Agile product managers have been advised to prioritize based on “business value.” While this seems an appropriate goal, it is vague and provides little specific guidance. Our approach to optimizing “business value” uses tactics to minimize costs and maximize benefits through strategic learning. In order to provide specific and actionable advice to agile product managers, we present two guidelines. These guidelines are meant to provide a set of considerations and a process by which an agile product manager can achieve the goal of optimizing “business value” while recognizing that different product managers will vary in their notions of what “business value” is.</description><subject>Agile Software Development</subject><subject>Analytic Hierarchy Process</subject><subject>Applied sciences</subject><subject>Computer science; control theory; systems</subject><subject>Exact sciences and technology</subject><subject>Product Manager</subject><subject>Software</subject><subject>Software engineering</subject><subject>Strategic Learning</subject><subject>User Story</subject><issn>0302-9743</issn><issn>1611-3349</issn><isbn>3540350942</isbn><isbn>9783540350941</isbn><isbn>3540350950</isbn><isbn>9783540350958</isbn><fulltext>true</fulltext><rsrctype>conference_proceeding</rsrctype><creationdate>2006</creationdate><recordtype>conference_proceeding</recordtype><recordid>eNpNkE9LAzEQxeM_sNae_AK5ePCwmtlJss2xLK0KBT3oUZY0m62pNVmSFdRPb0oFncsbeG8G3o-QC2DXwFh1A1BVHErVgDogZyg4Q8GUYIdkBBKgQOTq6M_g5TEZMWRloSqOp2SS0oblQagkVCPycu9NiH2IenB-TZdWR79btG_p_LO3ZrAtrUMaaOho_ar92lLn6WN0IbrBfe-yC6uHj2gTDZ7O1m5rsx02-TSdk5NOb5Od_OqYPC_mT_VdsXy4va9ny6IvQQ2FlhorM0VUUoipZLY0UrcS-IqLTrdqxbDtcplWydZasB2XxhgtoBNThSXimFzu__Y6Gb3tovbGpaaP7l3Hr4wKmECpcu5qn0vZylViswrhLTXAmh3c5h9c_AFphmck</recordid><startdate>2006</startdate><enddate>2006</enddate><creator>Harris, R. Scott</creator><creator>Cohn, Mike</creator><general>Springer Berlin Heidelberg</general><general>Springer</general><scope>IQODW</scope></search><sort><creationdate>2006</creationdate><title>Incorporating Learning and Expected Cost of Change in Prioritizing Features on Agile Projects</title><author>Harris, R. Scott ; Cohn, Mike</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-p219t-a6a37c8339655860e2c6ad614b45fad9b03df509d96dee1ef46ccca51f5893233</frbrgroupid><rsrctype>conference_proceedings</rsrctype><prefilter>conference_proceedings</prefilter><language>eng</language><creationdate>2006</creationdate><topic>Agile Software Development</topic><topic>Analytic Hierarchy Process</topic><topic>Applied sciences</topic><topic>Computer science; control theory; systems</topic><topic>Exact sciences and technology</topic><topic>Product Manager</topic><topic>Software</topic><topic>Software engineering</topic><topic>Strategic Learning</topic><topic>User Story</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Harris, R. Scott</creatorcontrib><creatorcontrib>Cohn, Mike</creatorcontrib><collection>Pascal-Francis</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Harris, R. Scott</au><au>Cohn, Mike</au><au>Succi, Giancarlo</au><au>Abrahamsson, Pekka</au><au>Marchesi, Michele</au><format>book</format><genre>proceeding</genre><ristype>CONF</ristype><atitle>Incorporating Learning and Expected Cost of Change in Prioritizing Features on Agile Projects</atitle><btitle>Extreme Programming and Agile Processes in Software Engineering</btitle><date>2006</date><risdate>2006</risdate><spage>175</spage><epage>180</epage><pages>175-180</pages><issn>0302-9743</issn><eissn>1611-3349</eissn><isbn>3540350942</isbn><isbn>9783540350941</isbn><eisbn>3540350950</eisbn><eisbn>9783540350958</eisbn><abstract>Very little has been written to date on how to prioritize and sequence the development of new features and capabilities on an agile software development project. Agile product managers have been advised to prioritize based on “business value.” While this seems an appropriate goal, it is vague and provides little specific guidance. Our approach to optimizing “business value” uses tactics to minimize costs and maximize benefits through strategic learning. In order to provide specific and actionable advice to agile product managers, we present two guidelines. These guidelines are meant to provide a set of considerations and a process by which an agile product manager can achieve the goal of optimizing “business value” while recognizing that different product managers will vary in their notions of what “business value” is.</abstract><cop>Berlin, Heidelberg</cop><pub>Springer Berlin Heidelberg</pub><doi>10.1007/11774129_19</doi><tpages>6</tpages></addata></record> |
| fulltext | fulltext |
| identifier | ISSN: 0302-9743 |
| ispartof | Extreme Programming and Agile Processes in Software Engineering, 2006, p.175-180 |
| issn | 0302-9743 1611-3349 |
| language | eng |
| recordid | cdi_pascalfrancis_primary_19105369 |
| source | Springer Books |
| subjects | Agile Software Development Analytic Hierarchy Process Applied sciences Computer science control theory systems Exact sciences and technology Product Manager Software Software engineering Strategic Learning User Story |
| title | Incorporating Learning and Expected Cost of Change in Prioritizing Features on Agile Projects |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-13T23%3A51%3A33IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-pascalfrancis_sprin&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.genre=proceeding&rft.atitle=Incorporating%20Learning%20and%20Expected%20Cost%20of%20Change%20in%20Prioritizing%20Features%20on%20Agile%20Projects&rft.btitle=Extreme%20Programming%20and%20Agile%20Processes%20in%20Software%20Engineering&rft.au=Harris,%20R.%20Scott&rft.date=2006&rft.spage=175&rft.epage=180&rft.pages=175-180&rft.issn=0302-9743&rft.eissn=1611-3349&rft.isbn=3540350942&rft.isbn_list=9783540350941&rft_id=info:doi/10.1007/11774129_19&rft_dat=%3Cpascalfrancis_sprin%3E19105369%3C/pascalfrancis_sprin%3E%3Curl%3E%3C/url%3E&rft.eisbn=3540350950&rft.eisbn_list=9783540350958&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rfr_iscdi=true |