About Dan Radigan

News:I've recently joined the Technical Account Management team helping customers go deep and scale great experiences with Atlassian tools. Interested? Check out my intro blog to learn more. Find me on Twitter: @danradigan.

Archives for Dan Radigan

Who’s who in agile teams?

Agile teams are structurally different than their waterfall counterparts. Agile teams focus on the team itself, whereas waterfall teams often follow the structure of the organization. As I was learning scrum, one of the questions that kept coming to mind was, “How do development managers and scrum masters share responsibilities in the team?” Let's explore the answer to this question.

Continue reading »

3 steps to taming technical debt

Mounting technical debt is similar to damage caused by termites--left unchecked, both can cause major problems. When technical debt creeps in, development becomes harder, the codebase becomes brittle, and tribal knowledge is required to understand hacks and known workarounds. Technical debt needs to be addressed and avoided in the future, but this is a difficult goal to strive for. Here at Atlassian, teams reduce technical debt by first identifying what it is, developing a plan to iteratively reduce it, and finding creative ways to enable developers to organically make the codebase better. Keep reading to learn more!

Continue reading »

Stand-up is one of the fundamental parts of agile development, and it’s often the most misunderstood. Let’s be real: stand-ups by themselves don’t make your team agile. They aren’t about inflating egos or justifying job descriptions. They aren’t a time to plan; Sprint planning is for planning. They also aren’t the only time to mention blockers. If you’re stuck, ask for help!

Continue reading »

Inside Atlassian: three steps for better sprint reviews

In the late afternoon on Fridays you can often hear clapping and cheering throughout the Atlassian office. Here, we work hard, play hard, and celebrate our successes in the form of sprint reviews. Sprint reviews are not retrospectives. A sprint review is about demonstrating the hard work of the entire team: designers, developers, and the product owner. At Atlassian we like to keep our sprint reviews casual. Team members gather around a desk for informal demos and describe the work they've done for that iteration. It's a time to ask questions, try new features, and give feedback. Sharing in success is an important part of building an agile team.

Continue reading »