Skip to main content

Home/ Agilesparks/ Group items tagged changes

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
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
Yuval Yeret

Scrum Breakfast: Scaling Scrum: SAFe, DAD, or LeSS? - 0 views

www.scrum-breakfast.com/...ng-scrum-safe-dad-or-less.html

scaling scrum agile SAFe LESS DAD scaling-agile-list

shared by Yuval Yeret on 28 Apr 14 - No Cached
  • LeSS is clearly in the Scrum and Agile tradition. It is the simplest of the three approaches and makes only a few changes to vanilla Scrum. When I look at Spotify, an organization that has scaled from 6 to 1200 staff members, I see a company architecture that is very close to LeSS. It will be a very natural approach for small organizations that are scaling up as they grow.
Yuval Yeret

The Kanban Method - Fixing Continuous Improvement - AgileIL12 by Yuval Yeret on Prezi - 0 views

prezi.com/...ntinuous-improvement-agileil12

kanban conference talk improvement journey yuvalyeret Continuous Improvement prezi improvement-list agile-change-management-list

shared by Yuval Yeret on 22 Mar 14 - No Cached
  • Yuval Yeret on 22 Mar 14
     
    "The Kanban Method - Fixing Continuous Improvement - AgileIL12 How Kanban provides a more sustainable and viable approach to Continuous Improvement by Yuval Yeret on 1 October 2012
Yuval Yeret

The Game of Team Culture - 1 views

www.infoq.com/...team-happiness-culture

twitterfavs agile change management infoq open agile adoption opt-in pull

shared by Yuval Yeret on 23 Mar 14 - No Cached
  • Yuval Yeret on 23 Mar 14
     
    How to Hack The Culture of Your Team (50min vid) http://t.co/GUB8tX0v3Y
Yuval Yeret

The Agile Fluency Project by James Shore — Kickstarter - 2 views

www.kickstarter.com/...the-agile-fluency-project

AgileFluencyProject twitterfavs agile-change-management-list

shared by Yuval Yeret on 02 Aug 14 - No Cached
  • Yuval Yeret on 02 Aug 14
     
    Check out the Agile Fluency Project immersion experience for a taste of Agile Done Well http://t.co/vQeqIaehck #AgileFluencyProject
  • Yuval Yeret on 02 Aug 14
     
    Check out the Agile Fluency Project immersion experience for a taste of Agile Done Well http://t.co/vQeqIaehck #AgileFluencyProject
« First ‹ Previous 61 - 78 of 78
Showing 20▼ items per page