Managing Product Development Chaos with Jira Software and Confluence
The document discusses managing product development chaos using Jira Software and Confluence, emphasizing the importance of clarity, efficiency, and visibility among stakeholders. It outlines the roles of different team members and executives, the challenges they face, and how Jira can help streamline product development with organized structures and answers to key questions. Overall, it highlights the benefits of using Jira to reduce confusion and improve collaboration across teams.
Introduction to managing product development and the role of the Product Manager.
Key steps in product development including planning, executing, testing, and measuring, and stakeholder needs for clarity, efficiency, and visibility.
Identifying challenges such as information overload, endless meetings, and asking if chaos is the only way to manage.
Jira Software enhances clarity, efficiency, and visibility in product management through organized workflows and backlog management.
Pros and cons of Jira Software, emphasizing its capabilities to streamline workflows, improve transparency, and reduce prep work.User feedback on Jira's effectiveness and a comparison of the situation before and after its implementation.
Product Development Steps
PlanExecute Test Measure
Requirements ready
to be broken down
Tickets reviewed and
merged to master
Verified end-end
against a test plan
Determine if feature
achieved success
4.
Stakeholders
Team Members
Focus onclarity
Team members includes engineering, design, and
quality assurance.
Questions asked include:
• Why is it important?
• Where do I focus?
• What is the solution?
5.
Stakeholders Focus onefficiency
Cross-functional includes product marketing, support,
sales, international and other product teams.
Questions asked include:
• Why is it important?
• What is the status?
• When will it be delivered?
Cross-Functional
6.
Stakeholders
Executives
Focus on visibility
Executivesinclude Head of Product, Head of
Engineering, and General Managers.
Questions asked include:
• Why is it important?
• What are the priorities?
• What are the results?
Information Overload
Endless Meetings
SlowComputers
Presentations, spreadsheets, and outdated
monolithic product requirements documents.
1:1 meetings focused on tribal knowledge,
prescriptive status meetings, and nonstop syncs.
Lots and lots of tabs open copying and pasting
content between emails, docs, tools, and chat.
• Learning curve
•Setup time and configuration
needed
PROS CONS
• Focus on resolving blockers
• Enables continuous
improvements
• Represents product
development steps
• Answers common
questions by stakeholders
26.
I really likethat this takes aspects
that were previously implicit and
makes them explicit.
- Engineering Manager
It makes sense and I love it. It
makes work easier and everything
is transparent for all teams.
- Quality & Assurance
Epics act as standing sources of
truth allowing me to update a
single source of truth, rather than
making changes to 6-7 linked
docs.
- Android Engineer
It saves me hours of prep work a
week. I love being able to see
different views without much
effort.
- Analyst