Software in 30 days: how agile managers beat the odds, delight their customers, and leave competitors in the dust
Gespeichert in:
| Hauptverfasser: | , |
|---|---|
| Format: | Buch |
| Sprache: | English |
| Veröffentlicht: |
Hoboken, N.J.
Wiley
2012
|
| Schlagworte: | |
| Online-Zugang: | Cover image Inhaltsverzeichnis |
| Beschreibung: | "A radical approach to getting IT projects done faster and cheaper than anyone thinks possibleSoftware in 30 Days summarizes the Agile and Scrum software development method, which allows creation of game-changing software, in just 30 days. Projects that use it are three times more successful than those that don't. Software in 30 Days is for the business manager, the entrepreneur, the product development manager, or IT manager who wants to develop software better and faster than they now believe possible. Learn how this unorthodox process works, how to get started, and how to succeed. Control risk, manage projects, and have your people succeed with simple but profound shifts in the thinking.The authors explain powerful concepts such as the art of the possible, bottom-up intelligence, and why it's good to fail early--all with no risk greater than thirty days. The productivity gain vs traditional "waterfall" methods has been over 100% on many projects Author Ken Schwaber is a co-founder of the Agile software movement, and co-creator, with Jeff Sutherland, of the "Scrum" technique for building software in 30 days Coauthor Jeff Sutherland was cosigner of the Agile Manifesto, which marked the start of the Agile movement Software in 30 Days is a must-read for all managers and business owners who use software in their organizations or in their products and want to stop the cycle of slow, expensive software development. Programmers will want to buy copies for their managers and their customers so they will know how to collaborate to get the best work possible"-- Provided by publisher. Includes bibliographical references and index |
| Beschreibung: | XVI, 194 S. Ill., graph. Darst. 24 cm |
| ISBN: | 9781118206669 |
Internformat
MARC
| LEADER | 00000nam a2200000zc 4500 | ||
|---|---|---|---|
| 001 | BV040447412 | ||
| 003 | DE-604 | ||
| 005 | 20170915 | ||
| 007 | t | ||
| 008 | 120928s2012 xxuad|| |||| 00||| eng d | ||
| 010 | |a 2011050969 | ||
| 020 | |a 9781118206669 |c pbk. |9 978-1-118-20666-9 | ||
| 035 | |a (OCoLC)815936977 | ||
| 035 | |a (DE-599)BVBBV040447412 | ||
| 040 | |a DE-604 |b ger |e aacr | ||
| 041 | 0 | |a eng | |
| 044 | |a xxu |c US | ||
| 049 | |a DE-91G |a DE-11 |a DE-M347 | ||
| 050 | 0 | |a QA76.76.D47 | |
| 082 | 0 | |a 005.1 | |
| 084 | |a SR 870 |0 (DE-625)143368: |2 rvk | ||
| 084 | |a ST 230 |0 (DE-625)143617: |2 rvk | ||
| 084 | |a ST 232 |0 (DE-625)143619: |2 rvk | ||
| 084 | |a DAT 345f |2 stub | ||
| 100 | 1 | |a Schwaber, Ken |d 1945- |e Verfasser |0 (DE-588)1082017493 |4 aut | |
| 245 | 1 | 0 | |a Software in 30 days |b how agile managers beat the odds, delight their customers, and leave competitors in the dust |c Ken Schwaber and Jeff Sutherland |
| 246 | 1 | 3 | |a Software in thirty days |
| 264 | 1 | |a Hoboken, N.J. |b Wiley |c 2012 | |
| 300 | |a XVI, 194 S. |b Ill., graph. Darst. |c 24 cm | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 500 | |a "A radical approach to getting IT projects done faster and cheaper than anyone thinks possibleSoftware in 30 Days summarizes the Agile and Scrum software development method, which allows creation of game-changing software, in just 30 days. Projects that use it are three times more successful than those that don't. Software in 30 Days is for the business manager, the entrepreneur, the product development manager, or IT manager who wants to develop software better and faster than they now believe possible. Learn how this unorthodox process works, how to get started, and how to succeed. Control risk, manage projects, and have your people succeed with simple but profound shifts in the thinking.The authors explain powerful concepts such as the art of the possible, bottom-up intelligence, and why it's good to fail early--all with no risk greater than thirty days. The productivity gain vs traditional "waterfall" methods has been over 100% on many projects Author Ken Schwaber is a co-founder of the Agile software movement, and co-creator, with Jeff Sutherland, of the "Scrum" technique for building software in 30 days Coauthor Jeff Sutherland was cosigner of the Agile Manifesto, which marked the start of the Agile movement Software in 30 Days is a must-read for all managers and business owners who use software in their organizations or in their products and want to stop the cycle of slow, expensive software development. Programmers will want to buy copies for their managers and their customers so they will know how to collaborate to get the best work possible"-- Provided by publisher. | ||
| 500 | |a Includes bibliographical references and index | ||
| 650 | 4 | |a Agile software development | |
| 650 | 4 | |a Scrum (Computer software development) | |
| 650 | 4 | |a Computer software |x Development | |
| 650 | 0 | 7 | |a Investitionstheorie |0 (DE-588)4162257-1 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Finanzanalyse |0 (DE-588)4133000-6 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Agile Softwareentwicklung |0 (DE-588)4806620-5 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Portfoliomanagement |0 (DE-588)4115601-8 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Risikomanagement |0 (DE-588)4121590-4 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Scrum |g Vorgehensmodell |0 (DE-588)7612008-9 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Kapitalanlage |0 (DE-588)4073213-7 |2 gnd |9 rswk-swf |
| 689 | 0 | 0 | |a Agile Softwareentwicklung |0 (DE-588)4806620-5 |D s |
| 689 | 0 | 1 | |a Scrum |g Vorgehensmodell |0 (DE-588)7612008-9 |D s |
| 689 | 0 | |5 DE-604 | |
| 689 | 1 | 0 | |a Investitionstheorie |0 (DE-588)4162257-1 |D s |
| 689 | 1 | 1 | |a Kapitalanlage |0 (DE-588)4073213-7 |D s |
| 689 | 1 | 2 | |a Finanzanalyse |0 (DE-588)4133000-6 |D s |
| 689 | 1 | 3 | |a Portfoliomanagement |0 (DE-588)4115601-8 |D s |
| 689 | 1 | 4 | |a Risikomanagement |0 (DE-588)4121590-4 |D s |
| 689 | 1 | |5 DE-604 | |
| 700 | 1 | |a Sutherland, Jeff |d 1941- |e Verfasser |0 (DE-588)108204685X |4 aut | |
| 776 | 0 | 8 | |i Erscheint auch als |n Online-Ausgabe |z 978-1-118-22854-8 |
| 776 | 0 | 8 | |i Erscheint auch als |n Online-Ausgabe |z 978-1-118-24090-8 |
| 776 | 0 | 8 | |i Erscheint auch als |n Online-Ausgabe |z 978-1-118-26574-1 |
| 856 | 4 | |u http://catalogimages.wiley.com/images/db/jimages/9781118206669.jpg |3 Cover image | |
| 856 | 4 | 2 | |m HBZ Datenaustausch |q application/pdf |u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=025295130&sequence=000004&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |3 Inhaltsverzeichnis |
| 999 | |a oai:aleph.bib-bvb.de:BVB01-025295130 | ||
Datensatz im Suchindex
| _version_ | 1804149506657222656 |
|---|---|
| adam_text | Titel: Software in 30 days
Autor: Schwaber, Ken
Jahr: 2012
Contents
About the Authors xi
Acknowledgments xiii
Introduction xv
Section I Why Every Business in the World Can Produce Software
in 30 Days 1
You are probably frustrated with your software organization. You would like it to
be quicker, more flexible, understand your needs better, and help you become
more profitable. We look at why you are frustrated and how to fix the problem.
1 The Crisis in Software: The Wrong Process Produces the Wrong Results 3
Many software organizations follow a development process that guarantees
waste, uncontrolled risk, unpredictability, surprises, and low value. We will
investigate why this process was chosen, how it guarantees failure, and look
and some organizations that have recovered from it.
2 Scrum: The Right Process Produces the Right Results 17
There is a process that is appropriate for software development. When you get
your developers to use it, you will immediately gain productivity, quality, value,
control, predictability, and satisfaction. We look at how this happens in
this chapter.
3 Try It Yourself: The Pilot 33
You have read our assertion that there is a better way for you to get software
developed for you. However, a lot of people have made assertions and taken
a lot of your money in the past, with little or no improvement. In this chapter
we show you how to prove that our approach works for no money.
4 What Can I Do? 49
You learned how to do better and you ve tried it yourself. You like the results
and you know what to tell the software organization to do. In this chapter, we
look at what you can do to help what you experience in the pilot project succeed.
Section II How to Produce Software in 30 Days 55
Having better software developed for your needs is not so much hard as
it is different from what you are used to. In this section, we look at a
progressively beneficial set of approaches to get you from where you are
now to organizational agility.
5 Getting Started with Scrum 57
Our secret sauce for improving your benefits from software is called
Scrum. Yes, this is the rugby event that keeps the ball moving down
the field. We ll discuss Scrum, how it works, and why it works in this chapter.
6 Scrum at the Project Level 63
Most persistent improvement in software development starts at the
project level. You can use Scrum to further prove its utility, or on
critically important initiative that must succeed. We ll explore what
you can tell your developers to do after reading this chapter.
7 Develop a Scrum Capability 75
Success often breeds success. As more software initiatives using
Scrum succeed, more people will want to get on the wagon. Rather
than changing the entire organization, let s look at how we can set up
a software development universe separate from the disappointing,
existing department. You can increasingly reap benefits here on an
increasing number of projects and releases.
8 Scrum at the Enterprise Level 101
Scrum at a project or release level provides initiative level agility, the ability
to rapidly respond to opportunities or rise to challenges. To gain the most
significant benefits, Scrum s empirical approach to software development
must befit into the organization as a whole. We ll look at how to do this,
and why some approaches are short-lived and others persist.
9 Enterprise Transformation: Profound and Persistent Change 107
You want to make your organization leaner, more efficient, and agile
on your watch. Even more, you want these benefits and their underlying
causes to persist and become the organizational culture. We ll look at
an enterprise change approach for achieving this in this chapter.
10 Scrumming Scrum 119
We devised Scrum for complex problem solving, like software development.
We found Scrum a useful technique for managing organizational change,
also a complex problem. The same benefits of transparency, waste removal,
risk control, and predictability occurred. We ll look at this use of Scrum
in this chapter.
Appendix 1: Terminology 127
We slowing and progressively introduced some new terminology. This appendix
is your reference for those terms.
Appendix 2: The Scrum Guide 133
Read the canonical guide to Scrum, its roles, artifacts, and events. This is
the bible of Scrum.
Appendix 3: A Playbook for Achieving Enterprise Agility 153
This appendix presents a more detailed plan for enterprise change, as
discussed in Chapter 10.
Index 185
|
| any_adam_object | 1 |
| author | Schwaber, Ken 1945- Sutherland, Jeff 1941- |
| author_GND | (DE-588)1082017493 (DE-588)108204685X |
| author_facet | Schwaber, Ken 1945- Sutherland, Jeff 1941- |
| author_role | aut aut |
| author_sort | Schwaber, Ken 1945- |
| author_variant | k s ks j s js |
| building | Verbundindex |
| bvnumber | BV040447412 |
| callnumber-first | Q - Science |
| callnumber-label | QA76 |
| callnumber-raw | QA76.76.D47 |
| callnumber-search | QA76.76.D47 |
| callnumber-sort | QA 276.76 D47 |
| callnumber-subject | QA - Mathematics |
| classification_rvk | SR 870 ST 230 ST 232 |
| classification_tum | DAT 345f |
| ctrlnum | (OCoLC)815936977 (DE-599)BVBBV040447412 |
| dewey-full | 005.1 |
| dewey-hundreds | 000 - Computer science, information, general works |
| dewey-ones | 005 - Computer programming, programs, data, security |
| dewey-raw | 005.1 |
| dewey-search | 005.1 |
| dewey-sort | 15.1 |
| dewey-tens | 000 - Computer science, information, general works |
| discipline | Informatik |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>04554nam a2200685zc 4500</leader><controlfield tag="001">BV040447412</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20170915 </controlfield><controlfield tag="007">t</controlfield><controlfield tag="008">120928s2012 xxuad|| |||| 00||| eng d</controlfield><datafield tag="010" ind1=" " ind2=" "><subfield code="a">2011050969</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781118206669</subfield><subfield code="c">pbk.</subfield><subfield code="9">978-1-118-20666-9</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)815936977</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV040447412</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">aacr</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="044" ind1=" " ind2=" "><subfield code="a">xxu</subfield><subfield code="c">US</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-91G</subfield><subfield code="a">DE-11</subfield><subfield code="a">DE-M347</subfield></datafield><datafield tag="050" ind1=" " ind2="0"><subfield code="a">QA76.76.D47</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">005.1</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">SR 870</subfield><subfield code="0">(DE-625)143368:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 230</subfield><subfield code="0">(DE-625)143617:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 232</subfield><subfield code="0">(DE-625)143619:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">DAT 345f</subfield><subfield code="2">stub</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Schwaber, Ken</subfield><subfield code="d">1945-</subfield><subfield code="e">Verfasser</subfield><subfield code="0">(DE-588)1082017493</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Software in 30 days</subfield><subfield code="b">how agile managers beat the odds, delight their customers, and leave competitors in the dust</subfield><subfield code="c">Ken Schwaber and Jeff Sutherland</subfield></datafield><datafield tag="246" ind1="1" ind2="3"><subfield code="a">Software in thirty days</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Hoboken, N.J.</subfield><subfield code="b">Wiley</subfield><subfield code="c">2012</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XVI, 194 S.</subfield><subfield code="b">Ill., graph. Darst.</subfield><subfield code="c">24 cm</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">"A radical approach to getting IT projects done faster and cheaper than anyone thinks possibleSoftware in 30 Days summarizes the Agile and Scrum software development method, which allows creation of game-changing software, in just 30 days. Projects that use it are three times more successful than those that don't. Software in 30 Days is for the business manager, the entrepreneur, the product development manager, or IT manager who wants to develop software better and faster than they now believe possible. Learn how this unorthodox process works, how to get started, and how to succeed. Control risk, manage projects, and have your people succeed with simple but profound shifts in the thinking.The authors explain powerful concepts such as the art of the possible, bottom-up intelligence, and why it's good to fail early--all with no risk greater than thirty days. The productivity gain vs traditional "waterfall" methods has been over 100% on many projects Author Ken Schwaber is a co-founder of the Agile software movement, and co-creator, with Jeff Sutherland, of the "Scrum" technique for building software in 30 days Coauthor Jeff Sutherland was cosigner of the Agile Manifesto, which marked the start of the Agile movement Software in 30 Days is a must-read for all managers and business owners who use software in their organizations or in their products and want to stop the cycle of slow, expensive software development. Programmers will want to buy copies for their managers and their customers so they will know how to collaborate to get the best work possible"-- Provided by publisher.</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Includes bibliographical references and index</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Agile software development</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Scrum (Computer software development)</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Computer software</subfield><subfield code="x">Development</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Investitionstheorie</subfield><subfield code="0">(DE-588)4162257-1</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Finanzanalyse</subfield><subfield code="0">(DE-588)4133000-6</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Agile Softwareentwicklung</subfield><subfield code="0">(DE-588)4806620-5</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Portfoliomanagement</subfield><subfield code="0">(DE-588)4115601-8</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Risikomanagement</subfield><subfield code="0">(DE-588)4121590-4</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Scrum</subfield><subfield code="g">Vorgehensmodell</subfield><subfield code="0">(DE-588)7612008-9</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Kapitalanlage</subfield><subfield code="0">(DE-588)4073213-7</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Agile Softwareentwicklung</subfield><subfield code="0">(DE-588)4806620-5</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">Scrum</subfield><subfield code="g">Vorgehensmodell</subfield><subfield code="0">(DE-588)7612008-9</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="689" ind1="1" ind2="0"><subfield code="a">Investitionstheorie</subfield><subfield code="0">(DE-588)4162257-1</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2="1"><subfield code="a">Kapitalanlage</subfield><subfield code="0">(DE-588)4073213-7</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2="2"><subfield code="a">Finanzanalyse</subfield><subfield code="0">(DE-588)4133000-6</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2="3"><subfield code="a">Portfoliomanagement</subfield><subfield code="0">(DE-588)4115601-8</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2="4"><subfield code="a">Risikomanagement</subfield><subfield code="0">(DE-588)4121590-4</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Sutherland, Jeff</subfield><subfield code="d">1941-</subfield><subfield code="e">Verfasser</subfield><subfield code="0">(DE-588)108204685X</subfield><subfield code="4">aut</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Online-Ausgabe</subfield><subfield code="z">978-1-118-22854-8</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Online-Ausgabe</subfield><subfield code="z">978-1-118-24090-8</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Online-Ausgabe</subfield><subfield code="z">978-1-118-26574-1</subfield></datafield><datafield tag="856" ind1="4" ind2=" "><subfield code="u">http://catalogimages.wiley.com/images/db/jimages/9781118206669.jpg</subfield><subfield code="3">Cover image</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="m">HBZ Datenaustausch</subfield><subfield code="q">application/pdf</subfield><subfield code="u">http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=025295130&sequence=000004&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA</subfield><subfield code="3">Inhaltsverzeichnis</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-025295130</subfield></datafield></record></collection> |
| id | DE-604.BV040447412 |
| illustrated | Illustrated |
| indexdate | 2024-07-10T00:24:07Z |
| institution | BVB |
| isbn | 9781118206669 |
| language | English |
| lccn | 2011050969 |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-025295130 |
| oclc_num | 815936977 |
| open_access_boolean | |
| owner | DE-91G DE-BY-TUM DE-11 DE-M347 |
| owner_facet | DE-91G DE-BY-TUM DE-11 DE-M347 |
| physical | XVI, 194 S. Ill., graph. Darst. 24 cm |
| publishDate | 2012 |
| publishDateSearch | 2012 |
| publishDateSort | 2012 |
| publisher | Wiley |
| record_format | marc |
| spelling | Schwaber, Ken 1945- Verfasser (DE-588)1082017493 aut Software in 30 days how agile managers beat the odds, delight their customers, and leave competitors in the dust Ken Schwaber and Jeff Sutherland Software in thirty days Hoboken, N.J. Wiley 2012 XVI, 194 S. Ill., graph. Darst. 24 cm txt rdacontent n rdamedia nc rdacarrier "A radical approach to getting IT projects done faster and cheaper than anyone thinks possibleSoftware in 30 Days summarizes the Agile and Scrum software development method, which allows creation of game-changing software, in just 30 days. Projects that use it are three times more successful than those that don't. Software in 30 Days is for the business manager, the entrepreneur, the product development manager, or IT manager who wants to develop software better and faster than they now believe possible. Learn how this unorthodox process works, how to get started, and how to succeed. Control risk, manage projects, and have your people succeed with simple but profound shifts in the thinking.The authors explain powerful concepts such as the art of the possible, bottom-up intelligence, and why it's good to fail early--all with no risk greater than thirty days. The productivity gain vs traditional "waterfall" methods has been over 100% on many projects Author Ken Schwaber is a co-founder of the Agile software movement, and co-creator, with Jeff Sutherland, of the "Scrum" technique for building software in 30 days Coauthor Jeff Sutherland was cosigner of the Agile Manifesto, which marked the start of the Agile movement Software in 30 Days is a must-read for all managers and business owners who use software in their organizations or in their products and want to stop the cycle of slow, expensive software development. Programmers will want to buy copies for their managers and their customers so they will know how to collaborate to get the best work possible"-- Provided by publisher. Includes bibliographical references and index Agile software development Scrum (Computer software development) Computer software Development Investitionstheorie (DE-588)4162257-1 gnd rswk-swf Finanzanalyse (DE-588)4133000-6 gnd rswk-swf Agile Softwareentwicklung (DE-588)4806620-5 gnd rswk-swf Portfoliomanagement (DE-588)4115601-8 gnd rswk-swf Risikomanagement (DE-588)4121590-4 gnd rswk-swf Scrum Vorgehensmodell (DE-588)7612008-9 gnd rswk-swf Kapitalanlage (DE-588)4073213-7 gnd rswk-swf Agile Softwareentwicklung (DE-588)4806620-5 s Scrum Vorgehensmodell (DE-588)7612008-9 s DE-604 Investitionstheorie (DE-588)4162257-1 s Kapitalanlage (DE-588)4073213-7 s Finanzanalyse (DE-588)4133000-6 s Portfoliomanagement (DE-588)4115601-8 s Risikomanagement (DE-588)4121590-4 s Sutherland, Jeff 1941- Verfasser (DE-588)108204685X aut Erscheint auch als Online-Ausgabe 978-1-118-22854-8 Erscheint auch als Online-Ausgabe 978-1-118-24090-8 Erscheint auch als Online-Ausgabe 978-1-118-26574-1 http://catalogimages.wiley.com/images/db/jimages/9781118206669.jpg Cover image HBZ Datenaustausch application/pdf http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=025295130&sequence=000004&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA Inhaltsverzeichnis |
| spellingShingle | Schwaber, Ken 1945- Sutherland, Jeff 1941- Software in 30 days how agile managers beat the odds, delight their customers, and leave competitors in the dust Agile software development Scrum (Computer software development) Computer software Development Investitionstheorie (DE-588)4162257-1 gnd Finanzanalyse (DE-588)4133000-6 gnd Agile Softwareentwicklung (DE-588)4806620-5 gnd Portfoliomanagement (DE-588)4115601-8 gnd Risikomanagement (DE-588)4121590-4 gnd Scrum Vorgehensmodell (DE-588)7612008-9 gnd Kapitalanlage (DE-588)4073213-7 gnd |
| subject_GND | (DE-588)4162257-1 (DE-588)4133000-6 (DE-588)4806620-5 (DE-588)4115601-8 (DE-588)4121590-4 (DE-588)7612008-9 (DE-588)4073213-7 |
| title | Software in 30 days how agile managers beat the odds, delight their customers, and leave competitors in the dust |
| title_alt | Software in thirty days |
| title_auth | Software in 30 days how agile managers beat the odds, delight their customers, and leave competitors in the dust |
| title_exact_search | Software in 30 days how agile managers beat the odds, delight their customers, and leave competitors in the dust |
| title_full | Software in 30 days how agile managers beat the odds, delight their customers, and leave competitors in the dust Ken Schwaber and Jeff Sutherland |
| title_fullStr | Software in 30 days how agile managers beat the odds, delight their customers, and leave competitors in the dust Ken Schwaber and Jeff Sutherland |
| title_full_unstemmed | Software in 30 days how agile managers beat the odds, delight their customers, and leave competitors in the dust Ken Schwaber and Jeff Sutherland |
| title_short | Software in 30 days |
| title_sort | software in 30 days how agile managers beat the odds delight their customers and leave competitors in the dust |
| title_sub | how agile managers beat the odds, delight their customers, and leave competitors in the dust |
| topic | Agile software development Scrum (Computer software development) Computer software Development Investitionstheorie (DE-588)4162257-1 gnd Finanzanalyse (DE-588)4133000-6 gnd Agile Softwareentwicklung (DE-588)4806620-5 gnd Portfoliomanagement (DE-588)4115601-8 gnd Risikomanagement (DE-588)4121590-4 gnd Scrum Vorgehensmodell (DE-588)7612008-9 gnd Kapitalanlage (DE-588)4073213-7 gnd |
| topic_facet | Agile software development Scrum (Computer software development) Computer software Development Investitionstheorie Finanzanalyse Agile Softwareentwicklung Portfoliomanagement Risikomanagement Scrum Vorgehensmodell Kapitalanlage |
| url | http://catalogimages.wiley.com/images/db/jimages/9781118206669.jpg http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=025295130&sequence=000004&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
| work_keys_str_mv | AT schwaberken softwarein30dayshowagilemanagersbeattheoddsdelighttheircustomersandleavecompetitorsinthedust AT sutherlandjeff softwarein30dayshowagilemanagersbeattheoddsdelighttheircustomersandleavecompetitorsinthedust AT schwaberken softwareinthirtydays AT sutherlandjeff softwareinthirtydays |