Agile Software Engineering with Visual Studio
From Concept to Continuous Feedback
Versandkostenfrei!
Nicht lieferbar
Using agile methods and the tools of Visual Studio 2010, development teams can deliver higher-value software faster, systematically eliminate waste, and increase transparency throughout the entire development lifecycle. Now, Microsoft Visual Studio product owner Sam Guckenheimer and leading Visual Studio implementation consultant Neno Loje show how to make the most of Microsoft's new Visual Studio 2010 Application Lifecycle Management (ALM) tools in your environment. This book is the definitive guide to the application of agile development with Scrum and modern software engineering practices u...
Using agile methods and the tools of Visual Studio 2010, development teams can deliver higher-value software faster, systematically eliminate waste, and increase transparency throughout the entire development lifecycle. Now, Microsoft Visual Studio product owner Sam Guckenheimer and leading Visual Studio implementation consultant Neno Loje show how to make the most of Microsoft's new Visual Studio 2010 Application Lifecycle Management (ALM) tools in your environment. This book is the definitive guide to the application of agile development with Scrum and modern software engineering practices using Visual Studio 2010.
You'll learn how to use Visual Studio 2010 to empower and engage multidisciplinary, self-managing teams and provide the transparency they need to maximize productivity. Along the way, Guckenheimer and Loje help you overcome every major impediment that leads to stakeholder dissatisfaction--from mismatched schedules to poor quality, blocked builds to irreproducible bugs, and technology "silos" to geographic "silos."Coverage includes / Accelerating the "flow of value" to customers in any software project, no matter how large or complex / Empowering high-performance software teams and removing overhead in software delivery / Automating "burndowns" and using dashboards to gain a real-time, multidimensional view of quality and progress / Using Visual Studio 2010 to reduce or eliminate "no repro" bugs / Automating deployment and virtualizing test labs to make continuous builds deployable / Using Test Impact Analysis to quickly choose the right tests based on recent code changes / Working effectively with sources, branches, and backlogs across distributed teams / Sharing code, build automation, test, project and other data across .NET and Java teams / Uncovering hidden architectural patterns in legacy software, so you can refactor changes more confidently / Scaling Scrum to large, distributed organizations Whatever your discipline, this book will help you use Visual Studio 2010 to focus on what really matters: building software that delivers exceptional value sooner and keeps customers happy far into the future. Foreword by Ken Schwaber It is my honor to write a foreword for Sam's book, Agile Software Delivery with Visual Studio.
Sam is both a practitioner of software development, as well as a scholar. I have worked with Sam for the last two years to merge Scrum with modern engineering practices and an excellent toolset, Microsoft's VS 2010. We are both indebted to Aaron Bjork of Microsoft, who developed the Scrum template that instantiates Scrum in VS 2010 through the Scrum Template.
I do not want Scrum to be prescriptive. I left many holes, such as what as the syntax and organization of the Product Backlog, the engineering practices that turned Product Backlog items into a potentially shippable increment, and the magic that would create self-organizing teams. Sam has superbly described one way of filling in these holes in his book.
He describes the techniques and tooling, as well as the rationale of the approach that he prescribes. He does this in detail, with scope and humor. Since I have worked with Microsoft since 2004 and Sam since 2009 on these practices and tooling, I am delighted.
Our first launch was a course, the Professional Scrum Developer .NET course, that taught developers how to use solid increments using modern engineering practices on VS 2010 -- working in self-organizing, cross-functional teams. Sam's book is the bible to this course and more, laying it all out in detail and philosophy. If you are on a Scrum Team building software with .NET technologies, this is the book for you.
If you are using Java, this book is compelling enough to read anyway, and maybe worth switching to .NET. When we devised and signed the Agile Manifesto in 2001, our first value was "Individuals and interactions over processes and tools." Well, we have the processes and tools nailed for the Microsoft environment. In Sam's book, we have something developers, who are also people, can use to understand the approach and value of the processes and tools.
Now the really hard work, people. After twenty years of being treated as resources, becoming accountable, creative, responsible people is hard. Our first challenge will be the people who manage the developers.
They could use the metrics from the VS 2010 tooling to micro-manage the processes and developers, squeezing the last bit of creativity out and leaving Agility flat. Or, they could use the metrics from the tools to understand the challenges facing the developers. They could then coach and lead them to a better, more creative and productive place.
This is the challenge of any tool. It may be excellent, but how it is used will determine its success. Thanks for the book, Sam.
Praise for Agile Software Engineering with Visual Studio "Agile dominates projects increasingly from IT to product and business development, and Sam Gucke
You'll learn how to use Visual Studio 2010 to empower and engage multidisciplinary, self-managing teams and provide the transparency they need to maximize productivity. Along the way, Guckenheimer and Loje help you overcome every major impediment that leads to stakeholder dissatisfaction--from mismatched schedules to poor quality, blocked builds to irreproducible bugs, and technology "silos" to geographic "silos."Coverage includes / Accelerating the "flow of value" to customers in any software project, no matter how large or complex / Empowering high-performance software teams and removing overhead in software delivery / Automating "burndowns" and using dashboards to gain a real-time, multidimensional view of quality and progress / Using Visual Studio 2010 to reduce or eliminate "no repro" bugs / Automating deployment and virtualizing test labs to make continuous builds deployable / Using Test Impact Analysis to quickly choose the right tests based on recent code changes / Working effectively with sources, branches, and backlogs across distributed teams / Sharing code, build automation, test, project and other data across .NET and Java teams / Uncovering hidden architectural patterns in legacy software, so you can refactor changes more confidently / Scaling Scrum to large, distributed organizations Whatever your discipline, this book will help you use Visual Studio 2010 to focus on what really matters: building software that delivers exceptional value sooner and keeps customers happy far into the future. Foreword by Ken Schwaber It is my honor to write a foreword for Sam's book, Agile Software Delivery with Visual Studio.
Sam is both a practitioner of software development, as well as a scholar. I have worked with Sam for the last two years to merge Scrum with modern engineering practices and an excellent toolset, Microsoft's VS 2010. We are both indebted to Aaron Bjork of Microsoft, who developed the Scrum template that instantiates Scrum in VS 2010 through the Scrum Template.
I do not want Scrum to be prescriptive. I left many holes, such as what as the syntax and organization of the Product Backlog, the engineering practices that turned Product Backlog items into a potentially shippable increment, and the magic that would create self-organizing teams. Sam has superbly described one way of filling in these holes in his book.
He describes the techniques and tooling, as well as the rationale of the approach that he prescribes. He does this in detail, with scope and humor. Since I have worked with Microsoft since 2004 and Sam since 2009 on these practices and tooling, I am delighted.
Our first launch was a course, the Professional Scrum Developer .NET course, that taught developers how to use solid increments using modern engineering practices on VS 2010 -- working in self-organizing, cross-functional teams. Sam's book is the bible to this course and more, laying it all out in detail and philosophy. If you are on a Scrum Team building software with .NET technologies, this is the book for you.
If you are using Java, this book is compelling enough to read anyway, and maybe worth switching to .NET. When we devised and signed the Agile Manifesto in 2001, our first value was "Individuals and interactions over processes and tools." Well, we have the processes and tools nailed for the Microsoft environment. In Sam's book, we have something developers, who are also people, can use to understand the approach and value of the processes and tools.
Now the really hard work, people. After twenty years of being treated as resources, becoming accountable, creative, responsible people is hard. Our first challenge will be the people who manage the developers.
They could use the metrics from the VS 2010 tooling to micro-manage the processes and developers, squeezing the last bit of creativity out and leaving Agility flat. Or, they could use the metrics from the tools to understand the challenges facing the developers. They could then coach and lead them to a better, more creative and productive place.
This is the challenge of any tool. It may be excellent, but how it is used will determine its success. Thanks for the book, Sam.
Praise for Agile Software Engineering with Visual Studio "Agile dominates projects increasingly from IT to product and business development, and Sam Gucke