Skip to main content

Home/ Agilesparks/ Group items tagged books

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Yuval Yeret

James Shore: The Art of Agile Development: Stories - 0 views

www.jamesshore.com/...stories.html

james shore stories product-ownership-101-list

shared by Yuval Yeret on 13 Jan 15 - No Cached
  • "Non-Functional" Stories AllyPerformance OptimizationPerformance, scalability, and stability—so-called non-functional requirements—should be scheduled with stories too. Be sure that these stories have precise completion criteria. See Performance Optimization for more.
  • Spike Stories AllySpike SolutionsSometimes programmers won't be able to estimate a story because they don't know enough about the technology required to implement the story. In this case, create a story to research that technology. An example of a research story is "Figure out how to estimate 'Send HTML' story". Programmers will often use a spike solution (see Spike Solutions) to research the technology, so these sorts of stories are often called spike stories.
Yuval Yeret

From the Agile Transformation Trenches: Culture Change with Pigs, not Chickens - 0 views

borland.typepad.com/...ge-with-pigs-not-chickens.html

Agile transition agilesparksblog

shared by Yuval Yeret on 07 Jul 09 - Cached
  • Identify the technical leaders within projects; those that are “self-driven to produce quality results on time … combine technical ability with enough people skills …are trusted and respected by both their managers and fellow developers, are determined to make the team succeed, and usually live the work.” (Chief programmers, Chapter 2:  A Practical Guide to FDD).
  • Sell them the vision: if you cannot sell these people on the benefits to them, their colleagues and the organization of the new way of working then something is wrong
  • Provide in-depth training and on-going coaching. It is better to have a single lead person trained in-depth who can coach his teammates through the basics than to have the whole team trained on the basics with no-one on the team to turn to when the basics are not enough.
  • ...3 more annotations...
  • Providing initial training is simply not enough. When the pressure is on, the temptation to return to previous ways of doing things is often too strong to resist. If technical leads are to work for you, they need on-going support and coaching, and a means by which they can support each other.  Good external coaches (expert chickens?) can help here.
  • Let the technical leads continue working on their projects. Some fail at the final hurdle by doing 1-3 above and then assigning or scheduling the technical leads to coach other projects, effectively turning them from pigs into chickens.
  • To summarize, if you can produce a change in the behavior of the lead pigs, the other pigs will, by definition, follow. However, pigs will not follow chickens for long because chickens are simply not pigs.
  • Yuval Yeret on 07 Jul 09
     
    Last month David Anderson wrote a two-part article on why agile transformation initiatives fail. David's suggestion to concentrate on cultural change reminded me of one of my favorite bits on process initiatives. From Peter Coad's book, Java Modeling in Color...
Yuval Yeret

All sizes | celebration zone | Flickr - Photo Sharing! - 0 views

www.flickr.com/...set-72157633394534958

twitterfavs

shared by Yuval Yeret on 23 Mar 14 - No Cached
  • Yuval Yeret on 23 Mar 14
     
    @DReinertsen I made an illustration inspired by your book. Hope it make sense. (optimal learning with experiments) http://t.co/g4SF2bSjhw
Yuval Yeret

» secrets of consulting :get LIT - 0 views

getlit.me/secrets-of-consulting

SecretsOfConsulting twitterfavs

shared by Yuval Yeret on 23 Mar 14 - No Cached
  • Yuval Yeret on 23 Mar 14
     
    Hot off the press, my visual-1-page-summary notes for the book #SecretsOfConsulting by @JerryWeinberg :: http://t.co/bj0TXumLoa
Yuval Yeret

James Shore: The Art of Agile Development: Spike Solutions - 0 views

www.jamesshore.com/...spike_solutions.html

james shore spike eng-practices-list

shared by Yuval Yeret on 13 Jan 15 - No Cached
  • About Spikes A spike solution, or spike, is a technical investigation. It's a small experiment to research the answer to a problem. For example, a programmer might not know whether Java throws an exception on arithmetic overflow. A quick ten-minute spike will answer the question.
  • Performing the Experiment The best way to implement a spike is usually to create a small program or test that demonstrates the feature in question. You can read as many books and tutorials as you like, but it's my experience that nothing helps me understand a problem more than writing working code. It's important to work from a practical point of view, not just a theoretical one.
  • Writing code, however, often takes longer than reading a tutorial. Reduce that time by writing small, standalone programs.
  • ...2 more annotations...
  • Design Spikes Sometimes you'll need to test some approach to your production code. Perhaps you want to see how a design possibility will work in practice, or you need to see how a persistence framework will work on your production code. In this case, go ahead and work on production code. Be sure to check in your latest changes before you start the spike and be careful not to check any of your spike code.
  • If you anticipate the need for a spike when estimating a story, include the time in your story estimate. Sometimes, you won't be able to estimate a story at all until you've done your research; in this case, create a spike story and estimate that instead
sagism

Reinventing Organizations: A Radically Inspiring Way to Work Together Kevan Writes - 0 views

www.kevanlee.com/reinventing-organizations

organizations self-organization

shared by sagism on 15 Feb 15 - No Cached
  • sagism on 15 Feb 15
     
    Summary of Frederic Laloux groundbreaking book
1 - 20 of 39 Next ›
Showing 20▼ items per page