Scrum in Action
Andrew Pham, Phuong-Van Pham
Language: English
Pages: 321
ISBN: 143545913X
Format: PDF / Kindle (mobi) / ePub
Andrew Pham, Phuong-Van Pham, "Scrum in Action"
English | ISBN: 143545913X | edition 2011 | Publisher: Course Technology PTR | PDF | 320 pages | 3,6 mb
SCRUM IN ACTION: AGILE SOFTWARE PROJECT MANAGEMENT AND DEVELOPMENT is a practical how-to guide for software project teams on how to successfully deploy an Agile software framework with Scrum. It is clearly and concisely written and is the first practical guide with real world situations written by corporate practitioners. This book describes many good project management techniques on how to get the most from project teams and bridges the gaps between many Scrum and project management books by addressing how to communicate with executives using financial terms, how to use an objective estimation technique, and where software architecture fits into Scrum.
The Dragon's Gift: The Real Story of China in Africa
concrete5 Beginner's Guide (2nd Edition)
jQuery Cookbook: Solutions & Examples for jQuery Developers
Sams Teach Yourself the Twitter API in 24 Hours
Lindstrom, Todd Little, Kent McDonald, Pollyanna Pixton, Preston Smith and Robert Wysocki.] Whether the Agile Manifesto and the Declaration of Interdependence (DOI) came to the experts’ minds first or after they had been somewhat influenced by Scrum or by any other then existing Agile processes, it does not really matter. What matters is that if your truly understand the meaning of the Manifesto and the DOI, you will have a leg up in adapting Scrum, should the need arise, without betraying its
calculation: a. The build fixed cost is higher than the buy fixed cost and the monthly buy fee is higher than the monthly build fee. In this case, the company should buy if it intends to keep the software product less than the calculated number of months. b. The buy fixed cost is higher than the build fixed cost and the monthly build fee is higher than the monthly buy fee. In this case, the company should build if it intends to keep the software product for less than the calculated number of
plan on keeping the software for more than 2 months, then we should build because the total cost of building ($1,000,000 þ $50,000 þ $50,000 þ $50,000 $1,150,000) will be less than the total cost of buying ($900,000 þ $100,000 þ $100,000 þ $100,000 $1,200,000). Normally, companies keep software for longer than two months, but this is an example for illustration purposes only. Net Present Value (NPV) Let’s talk about Present Value before we discuss Net Present Value (NPV) and Return on Investment
as among different members of the same Scrum team. 73 This page intentionally left blank Chapter 6 The Influence of Architecture Vision on Team Velocity and Software Quality (*) The title of this chapter may sound technical, but we hope we have presented the information in such a way that even the nontechnical person can understand the concepts covered in this chapter. Because it is very important for everyone on the Scrum team to understand what is meant by architecture and architecture
from Scrum projects, it has become clear that without an architecture vision, the chunk of user stories the teams get from the product owner will look like a stack of cards, without any clear idea of what the final product will look like. As a result, the team will have to spend time and effort trying to get the different stories to fit into some kind of blurred image of an ever-changing architecture. With a clear architecture vision laid down at the beginning, one observes that team velocity