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. Scott Theus of Parker Hannifin, 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!
Scott Theus, Senior Project Manager - IoT at Parker Hannifin
Parker Hannifin is the global leader in motion and control technology, producing precision engineered solutions for aerospace, climate control, electromechanical, and filtration systems — and that's not all. Currently, they're working with vendors to build software that connects energy grids to a cloud database, so failures can be addressed in real-time.
Within this world, Scott Theus takes a large role as a senior project manager and Atlassian administrator. He was perfectly placed to put Gliffy Project through its paces, and eager to do so. We were glad to have him in our beta test group.
In one of Scott's first practical applications of Gliffy Project, Scott used the tool to map out forward and backward paths for one of the projects on his plate. He and his team of engineers needed to get data from gateways in different sites on hydraulic pumps. The gateways sent food control sensor data from the pumps to the data lake, reporting on the condition of oil. From there, the data needed to get parsed, sorted, and analyzed for predictive maintenance.
His goal with Gliffy Project was to connect a macro, project-wide dependency diagram with more detailed insets, to which issues could be tagged, tackled, and tracked.
"I use a revised Product Based Planning model based on PRINCE2 to create a hierarchy of deliverables, then I create hot spots on each of the deliverables and add epics, stories, and tasks," says Scott. And so far, so good.
As Scott quickly grows familiar with Gliffy Project, he's finding how easy it is to add hotspots to a diagram and share the tasks with his team. Doing this lets him organize different layers of work and assess — visually — how he can effectively allocate team hours to different tasks.
"I’m a very visual person. Being able to show the team the order (in which tasks need to be completed) and show the links of the whole plan is very important for team progress."
Scott is the primary user of Gliffy Project at Parker Hannifin so far, but he sees how its usefulness is going to grow as his team and other teams begin to make it part of their processes. He's given his team a quick tour and they see the benefit of it, but there hasn't yet been time for them to get as excited about Gliffy Project as Scott is.