Friday, December 29, 2006

Bit by bit or all at once?

Posted by Simon Baker

From a very early age, we are taught to break apart problems. When we try to ‘see the big picture’, we try to reassemble the pieces in our minds, but this like trying to reassemble the fragments of a broken mirror to see a true reflection. After a while we give up trying to see the whole altogether.


Wednesday, December 27, 2006

Peacocks and penguins

Posted by Simon Baker

Friday, December 22, 2006

First incremental release of badjit

Posted by Simon Baker
For the last 8 weeks one of our teams has been developing an experimental application called badjit . And we've now put the first incremental release to production. The concept is simple - badjit is a social network that connects people via their shared passions. Visit badjit now and have your say. Say what you really think and explore what other people love and hate. Obviously, after only 8 weeks the functionality is basic but we've got a product backlog full of goodies coming in the New Year. The project was the brainchild of one of our product owner s. An objective of the project was to demonstrate that an idea could be taken from conception to production in a few weeks and without a requirements specification by using a co-located product owner and agile team .
Comments: 1

Sunday, December 17, 2006

Values, Practices & Principles

Posted by Gus Power
'What's the difference?!'

Saturday, December 9, 2006

ABC2006: Scaling agile

Posted by Simon Baker
Colin Bird said when you scale it's even more important to understand the principles (of the Agile Manifesto ). Damn right! So often they're compromised and you end up with something that just isn't that agile anymore. The practices also need to be consistent across the organisation. Here's what I took from the session: Start off with a beach-head team to build a head of steam. Create a cross-functional team from early evangelists and opinion leaders. Keep the team together long enough to succeed. Start small and make the team progressively larger over time, until it eventually becomes too big. Then split out people to seed new teams. Create enough cause for people in different teams to talk to one another. If you cannot avoid distributed teams, maximise communication with instant messengers and VOIP solutions; use an integrated development environment with a common continuous integration environment; cycle people through all teams. Avoid communities of common disciplines, e.g. DBAs or architects. Stagger daily stand-ups so that people from other teams can attend. Synchronise iterations to allow joint planning and delivery. More reading on Colin Bird 's blog: - Scaling agile - part 1 - Scaling agile - part 2

Agile finances?

Posted by Simon Baker
Tags: agile evm
Read more... Comments: 3

On average

Posted by Simon Baker
Here's the content of a presentation I recently put together based on some averages derived from how we've been working.

XPDAY2006: Joshua Kerievsky's keynote speech

Posted by Simon Baker
Tags: xpday
Joshua Kerievsky of Industrial Logic gave the first keynote speech at XPDay . He talked about selling agile methods. Here's what I took from the session:

Thursday, December 7, 2006

XPDAY2006: The Toyota Way of Managing

Posted by Simon Baker
Tags: lean, xpday
Read more... Comments: 3

Sunday, December 3, 2006

Ken Schwaber talks about agile quality

Posted by Simon Baker
Tags: quality, scrum
Ken Schwaber talks about Agile Quality: A Canary in a Coal Mine . If you get told to deliver specific functionality by a specific date that is impossible to attain without sacrificing quality, just say no . Remind the person who is effectively telling you to cut quality, that the software you're developing is a corporate asset . Do the right thing - don't build crap corporate assets.

Creative Commons Licence

Recent Posts

  1. Spark The Change - Innovation Governance
  2. Lean Day London 2014
  3. The Mechanics Of Meaning
  4. Engineering Design
  5. Debugging Grails Database Performance
  6. Grails for Hipsters
  7. Governance - Friend or Foe?
  8. The Energized Work lab is moving aboard ship
  9. Gus Power on the future of software development at The CW500 Club
  10. Agile On The Beach: Session: How Are We Doing?


  1. 2014 (4)
  2. 2013 (2)
  3. 2012 (27)
  4. 2011 (24)
  5. 2010 (31)
  6. 2009 (41)
  7. 2008 (69)
  8. 2007 (152)
  9. 2006 (128)
    1. December (16)
      1. Bit by bit or all at once?
      2. Peacocks and penguins
      3. First incremental release of badjit
      4. Values, Practices & Principles
      5. On average
      6. Agile finances?
      7. ABC2006: Scaling agile
      8. XPDAY2006: Joshua Kerievsky's keynote speech
      9. XPDAY2006: The Toyota Way of Managing
      10. XPDAY2006: Experiments in Agile Estimation
      11. Ken Schwaber talks about agile quality
      12. XPDAY2006: Keeping the Furniture Police at Bay
      13. XPDAY2006: Are We Nearly There Yet?
      14. Running tested features
      15. Ultimate extreme feedback device
      16. Gus has got a wiki going
    2. November (26)
    3. October (7)
    4. September (11)
    5. August (7)
    6. July (7)
    7. June (4)
    8. May (4)
    9. April (4)
    10. March (4)
    11. February (14)
    12. January (24)
  10. 2005 (63)
  11. 2004 (2)


agile (43) big visible chart (15) conference (43) culture (18) extreme programming (22) leadership (18) lean (47) people (27) planning (17) retrospective (18) scrum (41) story (19) team (30) testing (19) xpday (19)