As the problems we tackle get more complex, the nature of project teams is changing. Here’s what you need to know (and what you should change) in order to be successful.
Can you ever say with certainty that your project will be a success? Nope. You can’t. But running a premortem – a thought exercise in which you imagine what could go wrong and decide how to prevent it – in the early or middle stages of your project goes a long way.
Think about the last time you worked on a large group project. Go ahead — let out that inevitable groan. Now, think about the last time you worked on a group project that was completed ahead of schedule. Yep, we hear those crickets too. Team projects are notorious for taking far more time than expected, which means you don’t have to go far to find some famous examples.
Every time I get into a serious discussion about prioritization with the teams I coach, there’s a moment where someone does a big exhale (the kind where your cheeks puff out) and says “Let’s face it. We’re trying to do way too much and we’re kidding ourselves if we think we can do it at high quality.” And every time, they’re right.
We’ve heard from our enterprise customers that these problems are really hard to tackle – and they need our help along the way. That’s why we’re excited to share we’ve entered into an agreement to acquire AgileCraft, a leader in enabling scaled agile transformations. Many Atlassian customers, including AT&T, Anthem, NCR, TIAA, and Duke Energy trust AgileCraft to scale their teams’ agile practices.