Back to List

Relying Too Much On Tools and Technology (Agile Transformation Pain Point #9)

Rachael Wilterdink Rachael Wilterdink  |  
Nov 01, 2018
 
There are some wonderful tools out there, but you could literally just start with sticky notes on wall, especially if you're co-located.

If you aren’t co-located and are dispersed, that makes it quite a bit more challenging. But there are some tools that you can leverage to make that a bit easier. Once you've got the board down using the concept of Kanban columns for your product backlog, and sprint backlog, you can move the sticky notes across the board. It's fun, and there's something very cathartic about moving a sticky note to that done column, and you can jump up and down and have a celebration.
 
relying too much on tools and technology
 

Recommended digital tools

There are many great digital tools out there like Kanbanflow, Leankit, and Trello. There are also some other tools out there like Fun Retrospectives that can give you good ideas to keep your retrospectives fresh and avoid stagnating. There are also tons of requirements management tools. My favorite is Microsoft VSTS (pictured), but I've also used Jira.
 
digital kanban board
 

Avoid Excel for large project backlogs

I advise you to not do your backlog in Excel if you have a large project because it’s going to get unwieldy pretty darn quick. I would look at something more robust. But if you have a small project, there's nothing that says you can't just have your backlog on a spreadsheet. Also, there's a fun tool for doing your planning pokerwith dispersed teams that lets you flip all your cards at the same time.
 

Get a collaboration tool

Ideally, you should also get a collaboration tool like SharePoint, Slack or Microsoft Teams. That's another key piece of technology that can help you if you’re going to be agile.
 

Get the free eBook

This is the ninth of 20 blogs on 20 Agile Transformation Pain Points (and how to avoid or manage them). To read them all right now, download our free eBook.
 
agile transformation pain points ebook
Agile

 

Love our Blogs?

Sign up to get notified of new Skyline posts.

 


Related Content


Blog Article
Skipping Inspection and Adaptation (Agile Transformation Pain Point #20)
Rachael WilterdinkRachael Wilterdink  |  
Jan 31, 2019
Inspecting and adapting is one of the key parts of agile and Scrum. But over time, teams start to feel bored as if every session is the same.   If it does become boring, make sure you switch it up to keep it fresh. The Fun Retrospectives website has lots of ideas. Don’t skip this...
Jan 29, 2019
Jen Kalz is Featured on Mastering Business Analysis Podcast

We are excited to announce that Jen Kalz, Managing Consultant, is a featured guest on today's Mastering Business Analysis Podcast. Jen has known Dave Saboe, the man behind the Mastering Business Analysis site and podcast, for the last several years. She and Dave often speak at the same...
Blog Article
Distributed Global Challenges (Agile Transformation Pain Point #19)
Rachael WilterdinkRachael Wilterdink  |  
Jan 24, 2019
So far, I've been primarily discussing co-located teams, which is ideally better. However, this is the real world, and it's a global economy – most people don't have the luxury of being co-located.   If you have a team with dispersed team members, set up your working...
Blog Article
Accruing Technical Debt (Agile Transformation Pain Point #18)
Rachael WilterdinkRachael Wilterdink  |  
Jan 17, 2019
Everyone who works in technology probably knows that you already have a big pile of technical debt. The problem is that you are going to have to eventually pay that bill, and some of it is risky.     Dig out a little every Sprint You really need to be careful about technical...
Blog Article
Focusing On Projects Rather Than Products (Agile Transformation Pain Point #17)
Rachael WilterdinkRachael Wilterdink  |  
Jan 10, 2019
This is a difficult transition for waterfall companies to wrap their heads around. It's a big mindset shift that needs to happen to be truly successful. I'm not saying that you can't have an agile Scrum team that works on projects with a distinct beginning and end. That might be a...