Hundhausen Richard. - Professional Scrum Development With Microsoft Visual Studio 2012
Here you can read online Hundhausen Richard. - Professional Scrum Development With Microsoft Visual Studio 2012 full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:Professional Scrum Development With Microsoft Visual Studio 2012
- Author:
- Genre:
- Rating:5 / 5
- Favourites:Add to favourites
- Your mark:
Professional Scrum Development With Microsoft Visual Studio 2012: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Professional Scrum Development With Microsoft Visual Studio 2012" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Microsoft Press, 2012, 385 pp., Eng., ISBN: 978-0-7356-5798-4, EPUB
Introduction
Scrum is a framework for developing and sustaining complex products, such as software. Scrum is just a set of rules, as defined in the Scrum Guide (http://www.scrum.org/Scrum-Guides), and it describes the roles, events, and artifacts, as well as the rules that bind them together. When used correctly, this framework enables a team to address complex problems while productively and creatively delivering products of the highest possible value. Scrum is an Agile method. In fact, it is the most popular Agile method in use today.
Scrum employs an iterative and incremental approach to optimizing predictability and controlling risk. This is due to the empirical process control nature of Scrum. Through proper use of inspection, adaptation, and transparency, a Scrum Team can try a new way of doing something (an experiment) and gauge its usefulness after a short iteration. They can then collectively decide to embrace, extend, or drop the practice. This includes the tools a team uses and how they use them.
Combining Scrum with the application lifecycle management (ALM) tools found in Microsoft Visual Studio 2012 is a powerful combination. It is the purpose of this book to establish a baseline understanding of Scrum, as well as how Scrum is supported in Visual Studio 2012. I will also illustrate which practices provide more value when executed without the use of tools. In addition, I will point out those tools which have been erroneously marketed as healthy when used by a collocated, collaborative Scrum Team.
In software development, anything and everything can change in a moments notice. Healthy teams know this. They also know that continuously inspecting and adapting the way things are done is a way of life. High-performance Scrum Development Teams take it a step further. They know that within every dysfunction or impediment identified is an opportunity to learn and improve. Reading this book is a great first step.
Supplemental files and examples for this book can be found at http://examples.oreilly.com/9780735657984-files/.
Hundhausen Richard.: author's other books
Who wrote Professional Scrum Development With Microsoft Visual Studio 2012? Find out the surname, the name of the author of the book and a list of all author's works by series.
Professional Scrum Development With Microsoft Visual Studio 2012 — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Professional Scrum Development With Microsoft Visual Studio 2012" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Font size:
Interval:
Bookmark:
This book is dedicated to my Scrum Team: Esmay, Isla, Berlin, Blaize, Sawyer, and Kristen .
Supplemental files and examples for this book can be found at http://examples.oreilly.com/9780735657984-files/. Please use a standard desktop web browser to access these files, as they may not be accessible from all ereader devices.
All code files or examples referenced in the book will be available online. For physical books that ship with an accompanying disc, whenever possible, weve posted all CD/DVD content. Note that while we provide as much of the media content as we are able via free download, we are sometimes limited by licensing restrictions. Please direct any questions or concerns to .
Richard provides real Scrum guidance for real teams. If youre a Scrum team using Visual Studio, this book is a great resource.
Aaron Team Foundation Server, Microsoft Bjork
Richard successfully marries the best tools for .NET developers to the most effective practices without sacrificing the people.
David Visual Studio, Microsoft Starr
Finally, a book about Scrum from the Development Teams point of view; Richards description of the best and worst ways to implement Scrum is priceless. The first chapter alone is one of the best descriptions of Scrum done well that Ive ever seen.
Charles Bradley
The very first book on Team Foundation Server that I read was written by Richard, and hes done it again this time with another fantastic read.
Brian Keller
Richard does a fantastic job of blending theory, practice, and tools in one easy to read book! This book will surely be a staple for many of our Scrum coaching engagements.
Chad PST Albrecht
As an encore to helping introduce the industry shaking Professional Scrum Developer program, Richard reminds us in this book why hes a leading voice in Scrum and Visual Studio ALM.
Ryan MVP Cromwell
Ive known Richard a long time and its been great to follow his progression towards becoming a Scrum white robe. Im so happy the community now has the ultimate resource on understanding the marriage of Scrum and TFS.
Adam Visual Studio ALM MVP [of the year 2011] Cogan
If youre new to Scrum or even if youve been doing it for a while, this book will help you get the big picture.
Benjamin MVP Day
If youre using Scrum and TFS and you havent read this book, then youre probably doing it wrong.
Brian Visual Studio ALM MVP Randell
In this book, Richard uses the core values of Scrum to describe how to get the best Scrum adoption of Visual Studio 2012. This is a superb combination of principles and mechanics that should be on all teams bookshelves.
Simon Reindl
I dont keep a lot of technology books on my bookshelf due to the pace at which developer tools evolve but this book, with its focus on people and processes, is definitely a keeper. Richards book is to Scrum development as Petzolds was to Windows development.
Charles Microsoft Sterling
Among the plethora of Scrum literature out there, Richards book makes a difference by bringing Scrum closer to where it belongs: the day-to-day work in the context of a team, supported by suitable practices, and the state-of-the-art Visual Studio toolset. Youll benefit from most of the advice it contains, even if you dont use Visual Studio!
Jose PST Luis Soria
Scrum, Visual Studio, and Team Foundation Server are just tools, and they will not make you better by themselves. If you really want to improve you need to understand the tools and learn how to improve, and definitively, Richards book will help you to get there
Luis Visual Studio ALM MVP Fraile
A masterpiece which distills the world of Scrum in a Visual Studio environment; anyone who is using Scrum will recognize many of the smells and appreciate the sharing of real-world experience and guidance.
Willy-Peter Visual Studio ALM Rangers Schaub
This book should be required reading for everyone on your team. It will help you bring people, processes, and technology together quickly with Scrum.
Mike Visual Studio ALM MVP Vincent
By 2001, the software industry was in troublemore projects were failing than succeeding. Customers began demanding contracts with penalties, and increasingly sending work offshore. Some software developers, though, had increasing success with a development process known as lightweight. Almost uniformly, these processes were based on the well-known iterative, incremental process.
In February of 2001, these developers issued a manifestothe Agile Manifesto. The Manifesto called for Agile software development based on 4 principle values and 12 underlying principles. Two of the principles were 1.) to satisfy customers through early and continuous delivery of working software, and 2). to deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
By 2008, the Scrum Agile process was used predominantly. A simple framework, it provided an easily adopted iterative incremental framework for software development. It also incorporated the Agile Manifestos values and principles. The two authors of Scrum, Jeff Sutherland and myself, also were among the authors of the Agile Manifesto.
I had anticipated some of the difficulties organizations (and even teams) would face when they adopted Scrum. However, I believed that developers would bloom in a Scrum environment. Stifled and choked by waterfall, developers would stand tall, employing development practices, collaboration, and tooling that nobody had time to use in waterfall projects.
Much to my surprise, this was only true for perhaps 20 percent of all software developers.
In 2007, Martin Fowler characterized most Agile software development as flaccid. He stated: Theres a mess Ive heard about with quite a few projects recently. It works out like this:
They want to use an Agile process, and pick Scrum.
They adopt the Scrum practices, and maybe even the principles.
After a while, progress is slow because the code base is a mess.
Whats happened is that they havent paid enough attention to the internal quality of their software. If you make that mistake youll soon find your productivity dragged down because its much harder to add new features than youd like. Youve taken on a crippling Technical Debt and your Scrum has gone weak at the knees. (And if youve been in a real scrum, youll know thats a Bad Thing.) http://martinfowler.com/bliki/FlaccidScrum.html
Martins description of flaccid Scrum resonated with our experience. Most developers were skilled, but not adequately skilled in the three dimensions required to rapidly build complete increments of usable functionality. These dimensions are:
People The ability to work in a small, cross-functional, self-organizing team.
Practices The knowledge of and ability to apply modern engineering practices that short cycle development mandates.
Tooling Tools that integrated and automated these practices so that successive increments could be rapidly integrated without the drag of exponentially accruing artifacts that must be handled manually.
We put our business on hold while we worked through 2008 to create what has become known as the Professional Scrum Developer program. Offered in both a three- and five-day format, we formulated a workshop. The input was developers whose knowledge and capabilities produced flaccid increments. The output were teams of developers who had developed solid increments of software called for by the Agile Manifesto and demanded by the modern, competitive organization.
Font size:
Interval:
Bookmark:
Similar books «Professional Scrum Development With Microsoft Visual Studio 2012»
Look at similar books to Professional Scrum Development With Microsoft Visual Studio 2012. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Discussion, reviews of the book Professional Scrum Development With Microsoft Visual Studio 2012 and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.