There was a time when we complained about how long Microsoft Windows Updates would take to download and install to our machines. We setup “update” evenings to process all the updates that were in the backlog. Updates that were looked at and evaluated for close to three weeks before being applied to the servers. Now you wake up and 15 updates have been applied to your phone and a new feature has been installed to…
A new feature. A fix to an old bug. An idea for something new that you want to see whether there is some love from the market to keep it going? A direction you never thought of. A new platform of support. What should never be in a preview? Making your application harder to use then it was before. Putting your users through 5 clicks to accomplish a task that used to be done in…
Whenever we write requirements, we start off with a great big vision that we want to achieve. This is great in theory but when people read it, especially if they are mid to end of the release and work is not going well, they instinctively push it aside for – “nice to haves”, “if we can get to it”, “maybe next sprint”. But if we switch our mindset and instead write our features as challenges…
If you’re constantly forcing your team to hop between priorities and shiny objects, chances are your team will never get anything accomplished. Not for lack of trying but for lack of direction. The job of a leader is to keep the team’s eye on the goal, on the prize, on the delivery. Any external influences coming in are the Leader’s job to handle and keep off the team. And if you’re worried about your team…
A void in leadership can demotivate a team from 100 to 0 in seconds. Where everyone is looking for an answer, a path, a direction, anything that they can follow as a guide, hearing nothing in return leaves you feeling stuck, lost and confused. So what do you do? Step 1, figure out what you can do. Step 2, do it. Step 3, bring people in to so they can become a part of what…