Warm-eingepackt Hier klicken Halloween 30 Tage lang gratis testen Cloud Drive Photos primedeals Learn More Nina Suess Neuheiten Hier klicken Learn More Fire Kids Edition Shop Kindle PrimeMusic GC HW16
Profil für Ognjen Bajic > Rezensionen

Persönliches Profil

Beiträge von Ognjen Bajic
Top-Rezensenten Rang: 5.384.050
Hilfreiche Bewertungen: 1

Richtlinien: Erfahren Sie mehr über die Regeln für "Meine Seite@Amazon.de".

Rezensionen verfasst von
Ognjen Bajic

Seite: 1
Agile Software Engineering with Visual Studio, 2nd Edition (Microsoft .Net Development)
Agile Software Engineering with Visual Studio, 2nd Edition (Microsoft .Net Development)
von Sam Guckenheimer

1 von 1 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen The definitive guide on agile development with Visual Studio 2010, 10. November 2011
Agile software development methodologies have been proven on projects large and small. Nowadays methodology of choice is Scrum. It empowers multidisciplinary teams to successfully implement complex software and ensures the continuous flow of value through the development process.

This book will teach you how to successfully implement Scrum using integrated set of tools from Microsoft Visual Studio 2010 (VS) and the Team Foundation Server 2010 (TFS) and create automated process maximizing flow of value. In addition to the usual sprint and daily cycles, TFS based implementation of such process also exhibits micro cycles like check in and test. Ensuring the flow by making handoffs between team members as efficient as possible, by automating quality enforcing steps i.e. dones and gathering metrics without overhead at every cycle are cornerstones of this efficient process.

The book goes beyond teaching you how to apply Scrum using VS and TFS. Reinforcing the flow of value by introducing removal of waste (bug debt, partially implemented features, unfinished code etc.) impeding the flow and transparency pinpointing the weak spots in the process, further ensure success of the development project. Guckenheimer and Loje teach how to identify different types of waste and deal with them. They do a great job explaining how to read different reports and analyze dashboards to gain real-time insight in progress, quality and other aspects of your project.

VS and TFS aim at empowering the whole team.

Architects can analyze legacy code or continuously validate the current architecture with every daily build using layer diagram.
Developers will learn how to write clean code from the beginning and detect errors early. Different built in tools like check in policies or gated check-in help with that. Developers write or generate tests, check how effective they are and efficiently use them by executing only the tests impacted by a recent change from the set of all tests.
Testers use simple but efficient tools to find bugs and fill rich bug reports (backed by video recording, debugger level Intellitrace information, test steps etc.). Such bugs are easily reproducible and can be quickly analyzed and resolved.
Automated tests executed in virtualized test environments as a part of the build process with automated deployment are very powerful means to fight regressions.

In the third part of the book, author shares valuable experiences from Microsoft, where the team that produces TFS and VS struggled with quality and schedule. By introducing many of the same techniques described in the book, in the last several years, they regained control. The last chapter shows glimpses of the future tools from the VS vNext.

The authors of this book succeeded in two conflicting tasks: to offer clear, high level overview of modern agile software engineering practices on one side and on the other to dig deep enough in all the tools available in the Visual Studio 2010 and the TFS to show how they support these practices. Everything in an easy to read, moderately sized book.

I highly recommend this book to anyone involved with the software development, irrespective of the role they play. You will learn the proven practices and the toolset as well as the rationale for the prescribed development process.

Seite: 1