At this point, you have probably heard this term “Agile” either from Widen or maybe in your latest marketing meeting. It all sounds fine and dandy: software companies listening to their customers, teams favoring valuable outcomes over output and all touting a newfound ability to flex and adapt schedules based on changing technologies and customer input. However, coming from a former project manager, I get it, but I want to see it in action. How does “Wagile” work?
Let’s start with a real life, made-up scenario. You’re the web manager and your manager has decided that you should completely change your login process to make it easier for people to sign in to your company’s site. If you’re in an Agile shop, here’s a simplified outline of your project venture:
1) Team work session: During the team work session, your team works to understand the problem and business need, reviewing feedback you’ve heard from customers, and understanding why the change is needed and the outcomes expected.
2) Team storypointing session: During storypointing, each team member provides valuable input on how to solve the problem and the team discusses solutions from a user perspective. Stories are created based on those discussions. Each story represents a step in the login process. Team members assign a value to the story that represents the effort they need to make to complete the story. Values are used for planning what are known as sprints.
3) Customer testing/feedback and iterations: The team tests the software while listening to customer feedback and making changes as feedback is received. Rinse…repeat…until the team is ready to release a finalized product.
4) Deliver results in two-week iterations: This could mean small changes or big changes every couple weeks. Either way, iterations are broken up to deliver results in two-week increments.
The scenario above happens every day at Widen. As we speak, this week one team is beta testing prototypes of the analytics app and another team is storypointing additional file format enhancements, and every team is working its way towards an internal demo of the software, which is held every other week to show what’s been completed. We feel the Wagile process creates superior team communication which equals better software and happy customers.
Here’s what you can expect from Widen during our Wagile transformation.
- More visibility for you into what changes, enhancements and improvements we make. We will deliver notifications about enhancements and improvements via our new Topline in-app messaging and change history.
- More frequent releases. We’re committing to new changes delivered to your site every four weeks. We’ll keep you posted via Topline, our new in product messaging service.
- We need to hear from you, now more than ever. We need your input on our iterative designs, as feedback participants and idea generators. Email email@example.com to join fellow customers and/or submit ideas to widen.com/ideas.
Learn more at our Widen Summit. Attend the “Growing martech and going agile” session conducted by myself and Widen CEO Matthew Gonnering.