The document discusses how implementing Scrum can help address problems with existing projects. It outlines key principles of Agile and Scrum, including iterative development with frequent testing and delivery of working software. The workshop will cover strategy aspects of Scrum and share the presenter's personal experience using Scrum. Attendees will participate in an interactive activity to plan development of three civic tech apps over one year using Scrum methods.

1. te-st.ru
Alexey Sidorenko | Gdańsk | 04.04.2019
How to Stop Launching
Poor Projects
(and Love SCRUM)

2. te-st.ru
What to expect?
• Workshop lasts only 50 minutes;
• Workshop is aimed at project and product
managers;
• Workshop will cover strategy aspects of Scrum;
• It will be my personal experience (‘bastard
scrum’ possibility);
• Introvert alert: this workshop will include
interactive elements!

3. te-st.ru
Why me?

4. te-st.ru WordPress.org plugin download data
Effects of Scrum on existing projects
Before Scrum
implementation
With Scrum
implementation

5. te-st.ru
Problems that SCRUM can help with
• The result is different from the demand. Nobody
needs that stuff.
• The project’s launch is late.
• Project is launched in a ‘crap-beta’ state and not
properly tested.

6. te-st.ru
SCRUM – a lightweight, iterative and incremental
framework for managing product development. It
defines "a flexible, holistic product development
strategy where a development team works as a unit
to reach a common goal"

7. te-st.ru

8. te-st.ru
Key principles of Agile
#2 – Welcome changing requirements, even late in
development
#3 – Deliver working software frequently, from a couple
of weeks to a couple of months, with a preference to the
shorter timescale
#10 – Simplicity--the art of maximizing the amount of
work not done--is essential.

9. te-st.ru http://blog.innotas.com/waterfall-or-agile
Difference between ‘Waterfall’ and ‘Agile’
Big launch
Small
launch 1
Small
launch 2
Small
launch 3
Oh, crap, tests!
Ups! Oh, wow!

10. te-st.ru
Key Elements of Scrum

11. te-st.ru
1. Testing with
Stakeholders E A R L Y

12. te-st.ru
Testing environment:
prototypes (Figma), real life
installations

13. te-st.ru
2. Imagine what you want to
build

14. te-st.ru
https://www.businessinsider.com/heres-the-surprising-way-amazon-
decides-what-new-enterprise-products-to-work-on-next-2015-3?IR=T
Future Press Release Technique

15. te-st.ru
Happy Customer Letter technique:
«I always thought that in order to install your plugin I’ll need help of
an expensive IT specialist. They say, people used to hire volunteers to
do that. But with the new version, I just did it myself. Everything was
very clear and I knew what to do. And then, I just started to
fundraise…»

16. te-st.ru
Values of the product
(Simplicity, Security, Growth?)

17. te-st.ru
https://www.nathanialsmith.com/
2011/07/16/elephant-goals/

18. te-st.ru
Sprints – timeboxed iterations
no longer than one month and
most commonly two weeks

19. te-st.ru
Scrum teams (3-9 persons) can only focus on
properly developing a very limited number of
features per sprint – they form #Definition of
Done.

20. te-st.ru
No amendments should be
made to the current sprints

21. te-st.ru
Test after each sprint

22. te-st.ru
What is one year?

23. te-st.ru

24. te-st.ru
21 feature functions max

25. te-st.ru
Scrum team

26. te-st.ru
Removal of the hierarchy
1. Product owner
2. Scrum-master
3. Scrum team (3-9 persons)

27. te-st.ru
Interactive part
1. You’ll have 10 minutes
2. You’ll have 3 typical civic tech apps to develop
within 1 year
3. You’ll need to plan their development (in teams)

28. te-st.ru
Civic participation platform
1. Design template (buttons, style, etc.)
2. Registration workflow
3. Login / Log Out
4. On-boarding workflow
5. User profile
6. First page
7. Messaging between users
8. Official’s workflow
9. Mobile optimisation
10. Admin dashboard
11. Analytics system
12. Search workflow
13. Map
14. Issue submission tool
15. Issue solution workflow
16. Local Alerts functionality
17. Help and Documentation
18. Donation / Financial sustainability model
19. User growth functions
20. Gamification
https://www.fixmystreet.com/

29. te-st.ru
Public procurement platform
1. Design template (buttons, style, etc.)
2. Company Registration workflow
3. Login / Log Out
4. On-boarding company workflow
5. Company profile
6. Company’s validation workflow
7. First page
8. Messaging between users
9. Official’s registration workflow
10.Official’s profile
11.Official’s validation workflow
12.Mobile optimisation
13. Admin dashboard
14. Analytics system
15. Search workflow
16. Tender submission workflow
17. Help and Documentation
18. Donation / Financial sustainability model
19. User growth functions
https://prozorro.gov.ua/
20. Bilingual interface
21. Tender transaction history
22. Integration with procurement platforms API

30. te-st.ru
Police monitoring service
1. Design template (buttons, style, etc.)
2. Complaint submission tool
3. Registration workflow
4. Login / Log Out
5. On-boarding workflow
6. User profile
7. First page
8. Police representative’s workflow
9. Police department profile page
10.Police department profile page commenting / interaction system
11.Mobile optimisation
12. Admin dashboard
13. Analytics system
14. Search workflow
15. Map
16. Help and Documentation
17. Donation / Financial sustainability model
18. User growth functions
19. Gamification

31. te-st.ru
Discussion

32. te-st.ru
https://www.timeanddate.com/calendar/create.html