The software development silo is caused by tool differentials. When the dev team uses JIRA for project management, it silos SW dev from the rest of the organization, reduces transparency, and creates planning guesstimates.
Proggio might be the solution to the problem.
2. SOFTWARE DEVELOPMENT: AN OVERVIEW
Using dedicated
project
management tools
(JIRA)
Siloed from the
rest of the
organization
3. THE SILO IN ACTION:
THE UNCONNECTED ORGANIZATION
4. JIRA: THE PROS AND CONS
The Good:
• Familiarity: The dev team knows the
tool and is used to working with it
• Optimized for software development
and agile methodologies
• Dedicated software development tools
like bug tracking and issue management
The Bad:
• Organizational integrity: non-dev teams
don’t use JIRA
• JIRA lacks key project management
tools like budget tracking and load
balancing
• Lack of timeline view makes project
planning more guesstimate than reliable
plan
5. THE MAIN PROBLEM WITH JIRA
THE PLATFORM SHAPES HOW PROJECTS ARE MANAGED
By breaking down progress to tickets, issues are framed out of context
Progress is measured by pushing a ticket from “Backlog” to “Done” regardless of actual project
progress overall
This incentivizes the team members to work on one ticket at a time, outside of the project as a whole
Links between tickets are not portrayed, and poorly defined
INSTEAD OF A PROJECT, JIRA CREATES A TASK LIST
6. THE MISSING INGREDIENT: THE TIMELINE
Timelines are not just
for scheduling, they
are a key component
in project design
Without a timeline,
projects are just
unconnected tasks
requiring order and
flow
JIRA’s Kanban board
ticket based system for
tracking progress and
ordering workflow
creates the problem
7. Solution: A project management software that integrates with
JIRA, pulling data from JIRA and presenting it across a timeline.
This ends the software silo by providing transparency and overall
planning structure and provides a timeline view to the software
development team – within overall organizational plans.
8. HOW IT WORKS
Proggio’s JIRA Listener tool pulls data from JIRA and
presents it on the project plan timeline
10. The Projectmap is all inclusive: drill down
from PPM to individual team member tasks –
and back up again
From tasks to activity boxes,
from project plan to Portfolio
view, everyone in the team is
working with the same data, in
the same place, in real time.
12. THE TOTAL SOLUTION
Integrated project
management and
task management
Planning
capabilities
optimized for agile
methodology
Total visibility –
end of software
silo
Fully integrated
organization