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
Pre-assigning Work to Team Members (Agile Transformation Pain Point #14)
Rachael WilterdinkRachael Wilterdink  |  
Dec 13, 2018
This pain point is something you definitely don’t want to do. Agile and Scrum teams are meant to be self-organizing. They should volunteer to pick up assignments, not be assigned. Development team members are volunteering to do stories, and they might want to learn something new &ndash...
Blog Article
Taking on Too Much Work in a Sprint (Agile Transformation Pain Point #13)
Rachael WilterdinkRachael Wilterdink  |  
Dec 06, 2018
Some teams are super ambitious, and they just think they can climb a whole mountain in a single Sprint, but the whole goal with agile is to maintain a sustainable pace. Take on only what you really think you can get done within your Sprint. Don't overestimate your velocity, and don't...
Blog Article
Not Having a Definition of "Done" or "Ready" (Agile Transformation Pain Point #12)
Rachael WilterdinkRachael Wilterdink  |  
Nov 29, 2018
Most people who are familiar with agile are familiar with the concept of definition of Done. This is something that the team should create when they are first formed, and they should continually be inspecting and adapting that at each of their retrospectives. They can update that definition of...
Blog Article
Diagramming & Modelling Tips for Business Analysts
Kurt WondraKurt Wondra  |  
Nov 20, 2018
Among the many responsibilities of Business Analysts, including Backlog Management and Communicating and Collaborating with our teams, the skill of diagramming and modelling is one which seems to be more taboo than mainstream. Have you ever wondered why that is?   One observation I&rsquo...
Blog Article
Forgetting to Have the "Conversation" (Agile Transformation Pain Point #11)
Rachael WilterdinkRachael Wilterdink  |  
Nov 15, 2018
You may have heard the three C's of agile: the card, the conversation, and the confirmation. Many people will have the card: they'll write the story, but they'll forget about the other parts. They'll just write it in a silo and not get any feedback. They won’t actually...