Gliffy Project is a visual execution tool that enables teams to build more effectively by turning visual plans into Jira tasks. Or, said another way, it's how you take the visual plans you already use — diagrams, white board sketches, etc. — and translate them into action, side-stepping the normal pain points that crop up around communication.
There's a vision behind every project. Now, with Gliffy Project, that vision can become a tangible point of reference and a central repository upon which you can tag Jira tasks. This lets even dispersed teams stay on the same page, from project conception to launch.
But don't take our word for it. Jesse Carstens of Deckers, a participant in our beta test group, shares his hands-on experience with Gliffy Project. How does it work in the real world? How does it improve the development process? Let's see!
Jesse Carstens, Senior Manager eCommerce Operations & Technology at Deckers Outdoor Corporation
Look at your feet. There's a reasonable chance you're wearing a pair of shoes from Deckers, whose suite of brands include Ugg, Teva, and Sanuk. Jesse Carstens, the fellow in charge of technology at Deckers, needs to walk a mile in a lot of different shoes in order to support wholesale, retail, and e-commerce for the corporation.
In his first test run of Gliffy Project, Jesse created a swim-lane flowchart covering the company's buy online/pick up in store feature. This feature had initially rolled out fast and Jesse and his teams were looking to reduce some of the friction within the flow.
As product owner, Jesse uploaded a flowchart of the process into Gliffy Project and added hotspots directly to that diagram — with each hotspot automatically creating or linking to a Jira ticket on any number of boards.
"This concept is great," Jesse shares as soon as we get him on the phone. "I've got a product team that's half with me in Flagstaff, Arizona and then the rest are all over the world: Uganda, Russia..."
While Jesse doesn't have his team all working directly within Gliffy Project yet, he's already seeing improvements to their process. Because he can see his whole project process in one diagram and add issues directly to it, he gets a clear picture of dependencies and progress at a glance. What was complex and hard to articulate is now right in front of him.
"We've been using Gliffy Project for our story sessions. We walk through the work from the perspective of the developer add then add stories to the flowchart."
From there, Jesse assigns issues out to a mix of front-end and back-end teams so they can work towards the next weekly sync with the retail operations team. During these sessions, they all reference the master diagram in Gliffy Project. When new stories crop up, they just add them to the flowchart so they integrate within the big picture vision.
“It makes it very easy, visually, to see the overall health of our product," Jesse adds. Add that's good news, because it's part of what Gliffy Project was designed to make possible, and it's also a valuable shortcut when status reports need to be prepared. Which is all too often...
Jesse is continuing to use Gliffy Project and to integrate it into his development process.