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.

1. Managing Product Development
Chaos with Jira Software
and Confluence
RONALD LAI | PRODUCT MANAGER | STEALTH STARTUP | LAIRONALD@GMAIL.COM

2. CONGRATS
You are a
Product
Manager.

3. Product Development Steps
Plan Execute 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 on clarity
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 on efficiency
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
Executives include Head of Product, Head of
Engineering, and General Managers.
Questions asked include:
• Why is it important?
• What are the priorities?
• What are the results?

7. Needs of Stakeholders
Efficiency VisibilityClarity
Cross-functional ExecutivesTeam members

8. Information Overload
Endless Meetings
Slow Computers
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.

9. Is chaos the only way?

10. Let chaos reign.
Then reign in chaos.
ANDY GROVE, FORMER CEO OF INTEL

11. We believed it could be better

12. Jira Software
drive clarity,
efficiency,
and visibility.

13. Jira Software
Clarity

14. CLARITY WITH EPICS
Provides answers
Focus on blockers
Scales elegantly

15. How to organize?
Why?
What is the status?
Who are the stakeholders?
Who is responsible?
When?

16. How to organize?
What are the takeaways?
What is the work?

17. Jira Software Efficiency

18. EFFICIENCY WITH KANBAN
Provides answers
Focus on blockers
Scales elegantly

19. Product Development
Steps

21. Jira Software
Visibility

22. VISIBILITY WITH BACKLOG
Provides answers
Focus on blockers
Scales elegantly

23. Add a screenshot +
some bullet points
(similar to Sq deck)

24. Add a screenshot +
some bullet points
(similar to Sq deck)

25. • 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 like that 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

27. AfterBefore

28. RONALD LAI | PRODUCT MANAGER | STEALTH STARTUP | LAIRONALD@GMAIL.COM
Thank you!