Design thinking is gaining momentum as an optimal way to solve business and social problems. It is unique because it is not only the problem but also the people or systems impacted by the problem are considered.
As a continuous improvement exercise, retrospective meetings can use design thinking principles for improved results. In this post, you will learn how to put this in practice.
When customers approach a software development company and requests for a quotation, several factors come into play. Quality, reputation, cost are a few of them. However, Agility is the #1 thing that majority of customers want.
You’ve got the best performers in your team, yet they falter. You set reasonable deadlines for work to be completed, yet those deadlines are missed. You have tried a variety of collaboration tools and are yet unable to manage team cohesiveness. If these sound familiar to you, then it is time for you to take a step back and look at a different approach that can help you solve these challenges.
Can you work without weekends or vacation through a year? Unimaginable right! The same holds good with overworked agile teams. Why and how strategic breaks can help improve the team productivity is the topic of this post.Continue Reading
Let’s take it with a grain of salt. Not all retro meetings are fun. I have experience attending meetings where only the scrum master was speaking. Are retrospective meetings always dull? Can you make the team love the meetings? Here are 5 tips that you can use in your next meeting.Continue Reading