The document discusses the challenges in communication and information flow between developers and end-users and proposes solutions through structured information management and automated reporting. Emphasizing the importance of integration tools and collaboration, it outlines a DevOps approach to enhance feedback loops and streamline operations. The author highlights that clear structure and live data are crucial for effective project management and problem-solving.

1. Kārlis Broders
Manager at AA Projekts
Breaking barriers between
business and developers

2. The ignite plan:
1. Why?
• My experience
• Define the problem areas
2. A particular solution to the problems
• In a “DevOps” fashion (?!)

3. The ideal:
Fast and precise feedback
Developers End-users

4. Traceability
(in the real world)
Hey! Please send
me the latest
version of CR Nr.7!
Ok, not a problem!
Will bring it to you
the day after
tomorrow!

5. Monitoring
(a good guess)
UATs passed?Test coverage?
Defect count?
Can we
go live?
… or do
more
testing?
Reviewed and
Approved stories?

6. Collaboration
(my experience)
Project
consultant
Client
…or “a touch is worth a
thousand words” :)
Contracted
developer
Author: Anton Otto Fischer
The benefits of the face-
to-face meeting...

7. The problem list:
(recap)
• Hard to trace information
(missing context)
• Hard to find information on time
• Hence the disrupted communication
(no one has a clear picture)

8. The solution plan:
1. Structure information
• use tools
2. Connect the tools
• integrate and synchronize
3. Create automated LIVE reports (monitoring)

9. Key to structure is
using items!

10. Key to structure is
using items!

11. Tools to create
structure
And many more…

12. Why is integration
important?
To keep the data LIVE
and moving fast!
Manual “Copy-paste” kills!

13. How could integration
look like?
Tickets
End-users
Product manager
Developer
Features
User stories
User stories
Bugs
Tickets
Test cases
Test cases
User stories
Bugs
Test cases Developer

14. A beautiful loop
Code
Ops
QA / Sec

15. Why the separated teams?
• Preferred tools for each team or purpose
• Complex enterprise systems = many stakeholders
• Outsourced development
• Everyone sitting in the same room – !@£$?! How?!

16. A note on integration
tools
APIs are good, but require constant work!
• Ready made to integrate now
• Constant upgrades as APIs change
• Configurable mappings from UI

17. Automated reports

18. LIVE data = great and
automated reports
• Improves the quality of collaboration
Solving problems not arguing!Author: Anton Otto Fischer

19. The recap:
Problem area:
• Information flow between end-users and developers
A solution:
• Structure the information and automate the flow!
Failfast and repeat the cycle!

20. Thank you!
“…it's very hard to specify what you want in advance and be
correct […] easier to see something that's not quite right and
say how it needs to be changed.”
Martin Fowler