The reoccurring question for all Product Owners is: What should be built? It occurs in sprint planning: What should be built this sprint? It occurs in thinking about the near future: What should be built next? And it occurs when thinking further out: What should be built next year?
Here is our monthly selection of knowledge on programming, software testing and project management. This month you will find some interesting information and opinions about software architecture, performance testing, code reviews, Scrum sprint reviews, software requirements, user story mapping, agile coaching, IoT bugs and test automation.
The golden rules of Test-Driven Development (TDD) are: Don’t write source code until a test requires it Reference new classes, methods, variables etc in your test first, so the code won’t compile, and then fix it by declaring them Aim to have just one thing broken at a time if …
Here is our monthly selection of knowledge on programming, software testing and project management. This month you will find some interesting information and opinions about Google code reviews, Agile business analysis, code coverage, scaling scrum, toxic team members, non-deterministic testing, product roadmaps, performance testing, software design, containers, software architecture, technical …
Here is our monthly selection of knowledge on programming, software testing and project management. This month you will find some interesting information and opinions about product or feature teams, software architecture lock-in, Agile testing, team leadership, conflicts, the true nature of Agile, Scrum Master mistakes, serverless Java, test automation, exploratory …
A few years back, I was working with an organization where teams were achieving the expected increase in velocity, but leadership didn’t feel like things were moving any faster. Selecting one team, we looked at their history and found that their velocity had gone from an average of about 20 …
