Matches in Library of Congress for { <http://lccn.loc.gov/2011050969> ?p ?o. }
Showing items 1 to 25 of
25
with 100 items per page.
- 2011050969 alternative "Software in thirty days".
- 2011050969 contributor B12159737.
- 2011050969 contributor B12159738.
- 2011050969 created "c2012.".
- 2011050969 date "2012".
- 2011050969 date "c2012.".
- 2011050969 dateCopyrighted "c2012.".
- 2011050969 description "Includes bibliographical references and index.".
- 2011050969 description "Machine generated contents note: Section I: Why Every Business In The World Can Produce Software In Thirty Days This sections reviews how many organization struggle to develop software and how Software in Thirty Day's approach can eliminate the underlying problem. Chapter 1: The Crisis in Software: The Wrong Process Produces The Wrong Results Find out why so many software projects fail and why traditional methods are ill-suited to software development. Chapter 2: Scrum: The Right Process Produces the Right Results Understand the shift in thinking necessary to eliminate software project failure and deliver software in 30 days. Chapter 3: Try It Yourself: The Pilot You are interested. Learn how to run a pilot project that will successfully help you determine what to do next. Chapter 4: What Can I Do? Learn what you, as a manager, can do to make Software in 30 Days successful. Section II: Why Every Business In The World Can Produce Software In Thirty Days This section address how you can implement and embed Software in Thirty Days in your organization. Chapter 5: Getting Started with Scrum Understand how Scrum works. Chapter 6: Scrum at the Project Level Learn how to launch Scrum on a single project. Chapter 7: Develop a Scrum Capability Learn how to develop a Scrum capability in your organization. Chapter 8: Scrum at the Enterprise Level Consider spreading Scrum throughout the enterprise. Appendices 1: Terminology Look up terminology used in this book 2: Scrum Guide Read the canonical guide to Scrum 3: A Playbook for Achieving Enterprise Agility A Scrum enterprise adoption playbook in use since 1995.".
- 2011050969 extent "xvi, 194 p. :".
- 2011050969 identifier "9781118206669 (pbk.)".
- 2011050969 identifier 9781118206669.jpg.
- 2011050969 issued "2012".
- 2011050969 issued "c2012.".
- 2011050969 language "eng".
- 2011050969 publisher "Hoboken, N.J. : John Wiley & Sons, Inc.,".
- 2011050969 subject "005.1 23".
- 2011050969 subject "Agile software development.".
- 2011050969 subject "Computer software Development.".
- 2011050969 subject "QA76.76.D47 S3223 2012".
- 2011050969 subject "Scrum (Computer software development)".
- 2011050969 tableOfContents "Machine generated contents note: Section I: Why Every Business In The World Can Produce Software In Thirty Days This sections reviews how many organization struggle to develop software and how Software in Thirty Day's approach can eliminate the underlying problem. Chapter 1: The Crisis in Software: The Wrong Process Produces The Wrong Results Find out why so many software projects fail and why traditional methods are ill-suited to software development. Chapter 2: Scrum: The Right Process Produces the Right Results Understand the shift in thinking necessary to eliminate software project failure and deliver software in 30 days. Chapter 3: Try It Yourself: The Pilot You are interested. Learn how to run a pilot project that will successfully help you determine what to do next. Chapter 4: What Can I Do? Learn what you, as a manager, can do to make Software in 30 Days successful. Section II: Why Every Business In The World Can Produce Software In Thirty Days This section address how you can implement and embed Software in Thirty Days in your organization. Chapter 5: Getting Started with Scrum Understand how Scrum works. Chapter 6: Scrum at the Project Level Learn how to launch Scrum on a single project. Chapter 7: Develop a Scrum Capability Learn how to develop a Scrum capability in your organization. Chapter 8: Scrum at the Enterprise Level Consider spreading Scrum throughout the enterprise. Appendices 1: Terminology Look up terminology used in this book 2: Scrum Guide Read the canonical guide to Scrum 3: A Playbook for Achieving Enterprise Agility A Scrum enterprise adoption playbook in use since 1995.".
- 2011050969 title "Soft-ware in 30 days : how agile managers beat the odds, delight their customers, and leave competitors in the dust / Ken Schwaber and Jeff Sutherland.".
- 2011050969 title "Software in thirty days".
- 2011050969 type "text".
