Project Management meetup within "Open Technology Week" at Sigma Software Kharkiv.

1. ОPEN TECHNOLOGY
WEEK
Behind the Demo – Alexey Syrotyuk

2. SPEAKER’S INFO
 Alexey Syrotyuk, PMP, CoP
 Senior Project Manager
 Sigma Software
 Industry experience: 12 years
 alexey.syrotyuk@sigma.software

3. BEHIND THE DEMO
BUILDING TEAM CONTRIBUTION

4. GOOD PROJECT MANAGERS ADMIT MISTAKES:
THAT'S WHY YOU SO RARELY MEET A GOOD
PROJECT MANAGER 

5. METHODOLOGICAL ASPECT

7. CARGO CULT

8. SURVIVORSHIP BIAS

9. ASSASSINS CREED
“Nothing is true, everything is permitted”
Nothing is true: doubt, investigate, and try tools and process you borrow
Everything is permitted: take full responsibility for what you are doing

10. WHAT IS DEMO
 Review or Demo
 Empirical process control
 Demonstration is simply one step
 Demo energizes collaboration

11. CHANGING CONTEXT
Short feedback loop, value oriented
© http://agilemanifesto.org/
Inspect and adapt
Empirical process control
Onsite visits, colocation, video
Domain knowledge, product mindset

12. PITFALLS AND PROBLEMS
Boring or not in time Fix it 
No testimonials Show team contribution
Sporadic attendance Shall be worth time, educate
No sign-off Show earlier, control DoD
Useless project / tasks Focus on value, build mindset
High cost of change Contribute (Less is More, KISS)
Nothing to demo Think how to show

13. PREPARATION FOR DEMO
 Decide on attendees and schedule
 Define scenario and roles
 Share materials in advance
 Visualize complex rules and process flows
 Verify committed vs done work, list key decisions made

14. GENERAL RECOMMENDATIONS
Emotions matter Do not sound indifferent, offensive etc.
Be polite Use communication ethics
Sound professional At both technical aspects and language
Enjoy You present results of your work
Take pride You deliver tangible and valuable result
Stay calm When driver is in panic, passengers are scared
Don’t hurry Audience needs time

15. FOCUS ON BUSINESS VALUE
 Economically sensible outcome
 Define value at an early stage
 Propose smart solutions
 Start your story from the business value

16. TECHNICAL FEATURES DEMO
To demo or not to demo?
 To demo in most cases.
What to say?
 Why it was decided to go for it
 How the future work is affected
How to demo (for “code only”)?
 Project metrics (code coverage)
 Test results (green tests, performance
measurements etc.)

17. HOW TO DEMO REMOVED FEATURES

18. LEARN YOUR END USER

19. END USER EXPECTATIONS

20. PRODUCT ORIENTED MINDSET
PRODUCT ORIENTED MINDSET
Having solid understanding of the aim and
product benefits:
 Correct decision for implementation
 Ability to improve product
 More value for your client
 Satisfaction from what your are doing
TASK ORIENTED MINDSET
I did it as I was told
“First say to yourself what you would be;
and then do what you have to do”
— Epictetus

21. TEAM CONTRIBUTION

22. DOMAIN EXPERTISE
 Industry problems solved by the product
 Domain knowledge base
 Business area glossary
 Industry standards and constraints
 Competitive solutions analysis
 Review of 3rd party integrated systems

23. RECAP
 Learn tools and techniques, practices and their alternatives
 Dig to the gist of the above
 Doubt, analyze, take full responsibility
 Look under the hood of Demo, reveal more
 Apply same approach to other practices

24. REFERENCES
 https://www.slideshare.net/ChrisWebb6/last-conference-2016-agile-landscape-presentation-v1/4
 http://agilemanifesto.org/
 https://www.infoq.com/minibooks/kanban-scrum-minibook
 https://www.scrumalliance.org/community/spotlight/ken-rubin/january-2015/stop-calling-your-sprint-
review-a-demo%E2%80%94words-matte
 http://www.scaledagileframework.com/team-demo/
 http://agileforall.com/how-to-give-a-great-sprint-demo/

25. HAVE A GOOD DEMO!
PROJECT MAY GO WELL DESPITE ALL THE
PROJECT MANAGEMENT EFFORT 