Latest Post

Agile teams have more responsibility with less planning

Agile teams have more responsibility with less planning

Some people think agile teams have less responsibility because the plans are looser. In fact the opposite it true. When organisations start their agile journey, there are—inevitably—slips and confusion along the way. One thing that often happens is that the reduced up-front detailed planning leaves those outside a team to think there is “no planning” … Continue reading

Welcome

Hi. I'm Nik Silver. I've been leading software teams for years. My specialism is helping organisations work effectively with their technical teams, to deliver business value frequently and consistently. Take a look at my experience.

If you want to talk about turning talented people into brilliant teams then get in touch. I'm nik@niksilver.com on e-mail, and I'm @pigsaw on Twitter.

RSS Recently spotted

  • Doctrine — Medium
    Some excellent thoughts on using Wardley Maps - by Simon Wardley.
  • Minimize Design Risk by Focusing on Outcomes not Features
    "Teams who carefully consider users’ intents and needs produce better products because they know what people want and are not guessing what output might be best. The world is full of examples of useless products or features that nobody uses because they didn’t fill a need."
  • Does digital identity need blockchain technology? | GOV.UK Verify
    "Identity can be improved but it simply isn’t broken, so it’s hard to see where blockchain technologies are really required."
  • Censusfail and the fog of war | Risky Business
    "Last week I dashed off a very quick post about #CensusFail that went stupid viral. I think it was retweeted about 1200 times and it sort of became "the story" of what happened. [...] So, now that I've had a minute to breathe, let's look back through the bullet points in original post to see where it's solid and where it isn […]
  • Ye Olde Monolith - DZone Integration
    "Take a look at what it takes to make a monolith work (and the many, many ways it can go wrong at the code, developer, and organization levels)."