-
Psychological safety vs producive stress. How not to go #toxic.
Psychological safety vs producive stress is a conflict of interest. People usually think that much “safety” can lead to laziness ? Don’t rest on your laurels as they say ? On the other stress and some level of danger motivates us to harder work. Workplaces need a certain level of pressure to move forward. Deadlines, feedback, and responsibility all matter. But pressure is not the same as panic, and motivation is not the same as fear. The real challenge is to create an environment where people feel safe enough to speak honestly, while still being stretched enough to grow (or just get exploited and run down the mill?). Safety leads…
-
Do not be a hero – 3 pros and some tradeoffs
Do not be a hero. Why ? . Ever seen that one guy doing midnight fixes, hot releases after hours and then gets praised in front of everyone making You look bad ? When features are delivered on time and on target the team is considered heroes. We all love rewards and recognition but heroism might become … Heroes give up work / life balance. As the ancient wisdom teaches us “no good deed goes unpunished”. Whenever there is a new crisis or a target to achieve is set, yesterday’s heroes are quickly forgotten. Long hours eventually might lead to burnout, anxiety and/or even depression. What “Don’t Be a Hero”…
-
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…
-
Why agile is dead – Dave Thomas
Why agile is dead by Dave Thomas, one of the original co-authors of the Agile Manifesto, declared “Agile is Dead” in a candid and deeply insightful presentation. This provocative statement does not mean that agility—the underlying philosophy—is obsolete, but rather that the way Agile is practiced in many companies today has veered far from its original intent. Here he is a bit older ( and wiser ) then the main photo 🙂 Why agile is dead and what Is Agile ? At its core, Agile is a mindset—a commitment to being adaptable, valuing individuals and interactions over rigid processes, prioritizing working software over exhaustive documentation, fostering collaboration over contract negotiation,…
-
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…
-
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,…
