Werve.net Website Review

join my mailing list, and you too can learn from my mistakes experience. valuable articles on software engineering and team management, delivered hot and fresh to your inbox. no spam, not ever. at most 1-2 emails per week. thanks, but maybe some other time. it is not a great surprise that many companies struggle with growth, not because the cto is incompetent, but because most ctos are programmers that have had to rapidly pick up a set of skills that are entirely unrelated to. being a skilled programmer has as much connection to running a team as knitting sweaters for cats does to brain surgery. they both require a. sweater on a cat? – but that is where the connection ends. there are, of course, plenty of books on management, and a bottomless supply of consulting firms that will happily install some iso-certified agile process, but the reality is that while scrum, xp, or kanban make great. starting points, there is no one-size-fits-all process that will work everywhere without customization. the trick is to find a way to provide enough structure so that the team doesn’t go full cowboy and descend into total anarchy, while at the same time not constructing a bureaucratic nightmare worthy of a kafka novel. fortunately, there is a large box of management tools to rummage around in for solutions to problems like this, and what we are looking for is right near the top. agile, for all its problems, does provide one very effective tool that can help you and your team sort the bullsh*t from the beluga caviar, and it is the tool most often discarded in the interests of. bad process before it metastasizes into truly epic stupidity. as with any other management tool, it is important to understand what the tool does does and why it works, as without that understanding, it is far too easy for retrospectives to turn into little more than unfocused bi*ch with that in mind, let’s take a look at how an average team can apply scientific retrospectives to the process of team improvement, by sitting