-
Technical refinment – the power in agile sprint planning
Technical refinment In many Scrum teams, sprint planning sessions often suffer from the chronic problem of task underestimation. While teams aim for agility and velocity, frequently, the work selected for the sprint exceeds the actual capacity due to unclear or vague task definitions. This results in rushed implementation, increased bugs, and lengthy code reviews—ultimately slowing down delivery rather than speeding it up. This is where technical refinement comes in as a game changer. Technical refinement is a focused process during backlog refinement where the development team collaborates deeply to break down, clarify, and technically validate user stories and tasks before sprint planning begins. Technical refinment worth Key ways technical refinement…
-
Estimations in sprints are ludicrous ?
Estimations in sprints are ludicrous ? We switched from fibonacci complexity to just plain man day. Estimating work in sprints has become a cornerstone of Agile | Scrum methodologies More and more evidence suggests it often creates more problems than it solves. On the other hand it is a nice „form” You can wrap Your work into. It is a nice template. Teams routinely face mismatches between predicted complexity and actual time investment. Exacerbated by meetings that should be an email, administrative overhead and tasks like code reviews. The Fallacy of Sprint Estimation is why complexity metrics miss but do we have anything better ? The complexity is time disconnected…
-
Informed captain decision making in team
Informed captain decision making in team is another idea, from netlifx, to make everything in a company better, decentralized and so on and so forth. Fater, better harder stronger 😉 The generic idea is about „empowering teams and individuals” but here are the key points about this concept. Short story : Informed captain listens to everyone than is trusted to take the best decision to move forward. Informed Captain Responsibilities The captain owns the team’s mission, mandate, and metrics, and has full decision-making authority within their scope. Decision-Making Process Decisions are not made by consensus or committee votes. The captain has the final say after considering different viewpoints. Kinda like…
-
Estimating complexity vs time ….
Estimating complexity vs time… it cannot be done one without the other. First i will write why we should estimate complexity and then a very short point ’cause in the end…’. At least this might feel like it for some of us… Why should we estimate complexity in scrum Overall, estimating complexity versus time in Scrum promotes a deeper understanding of project requirements, enhances collaboration and communication within the team, and enables more accurate planning and risk management, ultimately contributing to the success of the project. Why estimating anything doesn`t really work I totally agree that splitting the task in smaller steps is the best thing we can do. Smaller,…
