By Dean Leffingwell
Contemplating going agile... unsure? get this publication. it really is full of sensible suggestion that incorporates years of expertise and knowledge!
Read or Download Scaling Software Agility: Best Practices for Large Enterprises PDF
Similar software development books
4 top-notch authors current the 1st ebook containing a catalog of object-oriented layout styles. Readers will how to use layout styles within the object-oriented improvement procedure, tips on how to resolve particular layout difficulties utilizing styles, and achieve a standard vocabulary for object-oriented layout.
Offers forty seven articles that characterize the insights and sensible knowledge of the leaders of the XP group. provide experience-based ideas for imposing XP successfully and gives winning transitioning techniques. Softcover.
Two-stage stochastic programming versions are regarded as appealing instruments for making optimum judgements less than uncertainty. regularly, optimality is formalized by means of making use of statistical parameters corresponding to the expectancy or the conditional worth in danger to the distributions of goal values. Uwe Gotzes analyzes an method of account for hazard aversion in two-stage versions established upon partial orders at the set of genuine random variables.
- Being Geek
- The Architecture of Privacy: On Engineering Technologies that Can Deliver Trustworthy Safeguards
- Systems: Brains of Corporations
- Industrial-Strength Formal Methods in Practice
Additional resources for Scaling Software Agility: Best Practices for Large Enterprises
There’s also a chance that you’ve missed an obvious Rolodex candidate. The reality is: Inclusion on the Rolodex is defined by the ability to survive job changes, although, paradoxically, you won’t actually know that for sure until you leave. Part of my inclusion criteria is that I see my relationship with this person as something larger than the current gig. If they’re on the Rolodex, it means I believe our relationship is no longer defined by the current job, and there’s no better way to test this hypothesis than switching gigs.
I know you love working on that new feature in the product—you’ll always love doing new things—but how about the busy work? How engaged are you in the work that is necessary but tedious? Remember when you joined the company and everyone was bright and you had no clue the boring work was, well, boring? Now that it’s boring, are you able to crank through it, or are you finding excuses to not do it? I’m not talking about a lull of interest; I’m talking about a complete lack of interest in the inane but essential work that moves the company forward.
You don’t open your mouth until you can feel the answer. My biggest interview pet peeve is when I ask a question and the candidate wastes three minutes of our time talking and never answering the question. The flawed reasoning here is that you need to say something immediately. But since you don’t immediately have an answer, you’re going to open your mouth and, hopefully, verbally wander toward one. This strategy can work, but when it fails, when you’re two minutes into a rambling answer that has nothing to do with what I asked, we’re both going to know it.