The Curious Engineer

All blogs / Software / engineering practice

Gojko's blog

gojko.net

How this affects the traditional PM role, and what other people need to prepare for

Software / engineering practiceTesting / QAEngineering management / careers

’10’15’20’25
Posts
187 from 11 Oct 2006 to 24 Jun 2026
Posting
now and then (1 in the last year)
Kind
personal blog
Feed
https://gojko.net/feed.xml

2026 1

  1. In five years, everyone will be a product manager

2024 1

  1. From Bugs to BEAM

2021 3

  1. Mega-workshop facilitation tips
  2. Nijute: how to solve impossible problems
  3. The Play, the points, and the biggest lie in software

2020 3

  1. Given-When-Then, tweak and try again
  2. Specification by Example, remotely
  3. Specification by Example, 10 years later

2019 4

  1. Descaling Agile
  2. Deliberate side-products
  3. Free card deck for 50 Quick Ideas to Improve User Stories
  4. BaDaaS and the future of cloud integration

2018 4

  1. Sprints, marathons and root canals
  2. Error Mining
  3. Choosing the right JavaScript testing tool
  4. Alice in the Hall of Mirrors

2017 13

  1. Christmas Prioritisation
  2. People that make computers go crazy
  3. The scary side of biometric security
  4. Five things everyone should know about Unicode
  5. Snow White and the 777.777.777 Dwarfs
  6. Introducing Appraise
  7. Designing for the Serverless Age
  8. Humans vs Computers finally shipping
  9. Names that make computers go crazy
  10. When automation goes horribly wrong
  11. Migrating to Serverless, an experience report
  12. The key lesson from our serverless migration
  13. To slice stories, first make sure they are TOO BIG

2016 12

  1. Impact Mapping With Innovation Games
  2. Migrating to a serverless architecture, MindMup 2.0 case study
  3. What's next for agile? -- interview at Agile Prague
  4. Awesome JS microservices in the cloud for (almost) free
  5. Highlights from Serverless Code Camp #1
  6. Serverless architectures: game-changer or a recycled fad?
  7. Five ways to reduce the cost of large test suites
  8. Impact Mapping Workshop – now opensource and free to use
  9. The key first step for successful organisational change
  10. The most important lesson to improve software delivery
  11. Introducing Claudia.js – deploy Node.js microservices to AWS easily
  12. Potentially shippable is no longer good enough

2015 7

  1. Test automation without a headache
  2. Automated testing: back to the future
  3. Turning continuous delivery into a business advantage
  4. Avoiding the most common pitfall of large-scale agile
  5. To improve testing, snoop on the competition
  6. Explore capabilities, not features
  7. How to get the most out of Given-When-Then

2014 13

  1. How to get the most out of impact mapping
  2. Adaptive Planning Beyond User Stories
  3. Zone of control vs Sphere of influence
  4. Specification by Example from Agile New Zealand 2014
  5. Make Impacts, not Software
  6. Forget the walking skeleton – put it on crutches
  7. Focus on key examples
  8. Throw user stories away after they are delivered
  9. Kanban in Action
  10. How to not just survive, but thrive with flexible scope
  11. Budget instead of estimating
  12. User stories should be about behaviour changes
  13. Divide responsibility for defining stories

2013 4

  1. Let's break the Agile Testing Quadrants
  2. Writing “As a User” does not make it a user story
  3. Scrum, velocity, and driving down the motorway the wrong way
  4. How we solved our #1 product management problem

2012 8

  1. BDD - busting the myths
  2. Reinventing software quality - video
  3. How To Solve “Not Enough Time”
  4. Redefining software quality
  5. Splitting user stories -- the hamburger method
  6. The February Revolution
  7. February revolution, part 2
  8. Sleeping with the enemy

2011 12

  1. Five Key Challenges for Agile Testers tomorrow
  2. Dan North at Oredev - Embrace Uncertainty
  3. Kiss and fly
  4. Clean Coder – sharpen your professional skill
  5. The Mistake at the Heart of Agile
  6. Bug statistics are a waste of time
  7. A fresh perspective on the specification/script problem
  8. Visualising quality - initial ideas
  9. The wolf who cried boy
  10. Is prioritisation based on business value right?
  11. Simulating your way out of regression testing
  12. TDD breaking the mould

2010 24

  1. The principle of symmetric change
  2. Beyond basic TDD
  3. Seven key ideas of real quality assurance
  4. How Google does test engineering
  5. Bug tracking for agile teams
  6. Rethinking user interface test automation
  7. Let’s change the tune
  8. The Sine of Death by UI Test Automation
  9. Stop automating manual test scripts!
  10. Anatomy of a good acceptance test
  11. Eric Evans -- Domain driven design redefined
  12. Evolution of DDD -- CQRS and Event Sourcing
  13. Udi Dahan -- the biggest mistakes teams make when applying DDD
  14. Effective root cause analysis techniques
  15. Agile in a Start-up Games Development Studio
  16. David Anderson's Kanban -- Finally an authoritative source on the Kanban method
  17. Effective exercises for teaching TDD
  18. How to implement UI testing without shooting yourself in the foot
  19. Mind your boomerangs
  20. Brian Marick -- Mocks lead to better design faster
  21. Acceptance testing best practices
  22. Are tools necessary for acceptance testing, or are they just evil?
  23. The Billboard over Moscow
  24. How to effectively define a sufficient set of BDD scenarios/Acceptance tests?

2009 34

  1. Challenging requirements
  2. Software process improvements with Lean and Kanban at BNP Paribas
  3. Improving testing practices at Google
  4. Eight interesting techniques to test how a project is going
  5. Growing Object Oriented Software, Guided by Tests
  6. How to test asynchronous systems efficiently
  7. Checking is not testing, testing is not checking
  8. Efficiency is the enemy of effectiveness
  9. QUPER model for better requirements
  10. Upgrading agile development at uSwitch.com - From concept to production in four days
  11. Mockito in six easy examples
  12. Mary Poppendieck - test driven development redefined
  13. How to promote learning in software teams
  14. Are agile testers different?
  15. Changing the role of test managers
  16. Seven key agile testing practices for releasable software
  17. DDD and relational databases – the value object dilemma
  18. Top 10 reasons why teams fail with Acceptance Testing
  19. Joe the Developer doesn't need a certificate
  20. Mocks are not about isolation, but about responsibilities
  21. Software development with hunters and gatherers
  22. To merge or not to merge code – essentially not an IT decision!
  23. Acceptance testing in plain English with Concordion .NET
  24. Building software that matters
  25. TDD as if you meant it – revisited
  26. Improving performance and scalability with DDD
  27. Eric Evans - Why do efforts to replace legacy systems fail?
  28. Examples make it easy to spot inconsistencies
  29. Eric Evans – What I’ve learned about DDD since the book
  30. Is software engineering?
  31. What have we learned from 10 Years of TDD?
  32. Thought-provoking TDD exercise at the Software Craftsmanship conference
  33. Agile Testing (Crispin/Gregory) is a great book, long overdue
  34. Messaging is not just for investment banks

2008 21

  1. Doing the wrong thing right is better than doing the right thing wrong
  2. Quality comes from cooperation
  3. Specification workshops - an agile way to get better requirements
  4. Specifying with examples
  5. How to test e-mail notifications properly
  6. Fitting agile acceptance testing into the development process
  7. How many points are there in a five-point star?
  8. Adopting agile from inside - learnings from the BBC
  9. The fifth element of the Agile Manifesto
  10. Paying programmers -- are bonuses bad and what to do about it?
  11. Bulding smart teams
  12. 10 ways to screw up despite Scrum and XP
  13. Programming Collective Intelligence
  14. The tale of two bridges
  15. Put the web server on a diet and increase scalability
  16. Delivering useful software
  17. Lazy web sites run faster
  18. Two data streams for a happy website
  19. When TDD goes bad
  20. How to avoid getting lost in translation
  21. Returning the favour for on-site customers

2007 15

  1. How to sell TDD to non-technical stakeholders?
  2. The waterfall trap for “agile” projects
  3. Who should write acceptance tests?
  4. Fighting the monster
  5. The Zero-Testing Time Bomb
  6. Effective user interface testing
  7. Don’t deal with problems like Gaggia
  8. The Poka-Yoke principle and how to write better software
  9. Documentation for Telepathic Developers
  10. Breaking the Web
  11. Agile Architect – Myth or Reality?
  12. Simple CV Spam Filter - if (certified) move(“junk”)
  13. How not to build a castle on a swamp
  14. Blinded by the user interface
  15. The Inmates Are Running the Asylum

2006 8

  1. Logging anti-patterns
  2. Moving from software production to software publishing
  3. The Magic of Goals -- Focused Projects and Better Requirements
  4. Sources of Power - How People Make Decisions
  5. Death March
  6. The Art of Project Management
  7. The Best Software Writing I
  8. How to develop software like commanding a tank