The document outlines the Agile Manifesto's 12 principles, emphasizing customer satisfaction through rapid software delivery, welcoming changes even late in development, and the importance of close collaboration between business and developers. It also discusses the roles of Scrum in team management and Lean in product management, along with data collection strategies for improving engagement through A/B testing and performance experiments. Lastly, it highlights the significance of a data-driven approach in decision-making and the need for proper data monitoring and validation.

1. FROM SCRUM
TO LEAN
VLAD MYSLA
JustAnswer | Ask a question get an answer ASAP

2. JustAnswer | Ask a question get an answer ASAP
The Agile Manifesto is based on 12 principles:
1.Customer satisfaction by rapid delivery of useful software
2.Welcome changing requirements, even late in development
3.Working software is delivered frequently (weeks rather than months)
4.Close, daily cooperation between business people and developers
5.Projects are built around motivated individuals, who should be trusted
6.Face-to-face conversation is the best form of communication (co-location)
7.Working software is the principal measure of progress
8.Sustainable development, able to maintain a constant pace
9.Continuous attention to technical excellence and good design
10.Simplicity—the art of maximizing the amount of work not done—is essential
11.Self-organizing teams
12.Regular adaptation to changing circumstances

3. JustAnswer | Ask a question get an answer ASAP
The Agile Manifesto is based on 12 principles:
1.Customer satisfaction by rapid delivery of useful software
2.Welcome changing requirements, even late in development
3.Working software is delivered frequently (weeks rather than months)
4.Close, daily cooperation between business people and developers
5.Projects are built around motivated individuals, who should be trusted
6.Face-to-face conversation is the best form of communication (co-location)
7.Working software is the principal measure of progress
8.Sustainable development, able to maintain a constant pace
9.Continuous attention to technical excellence and good design
10.Simplicity—the art of maximizing the amount of work not done—is essential
11.Self-organizing teams
12.Regular adaptation to changing circumstances

4. JustAnswer | Ask a question get an answer ASAP
The Agile Manifesto is based on 12 principles:
1.Customer satisfaction by rapid delivery of useful software
2.Welcome changing requirements, even late in development
3.Working software is delivered frequently (weeks rather than months)
4.Close, daily cooperation between business people and developers
5.Projects are built around motivated individuals, who should be trusted
6.Face-to-face conversation is the best form of communication (co-location)
7.Working software is the principal measure of progress
8.Sustainable development, able to maintain a constant pace
9.Continuous attention to technical excellence and good design
10.Simplicity—the art of maximizing the amount of work not done—is essential
11.Self-organizing teams
12.Regular adaptation to changing circumstances

5. JustAnswer | Ask a question get an answer ASAP
The Agile Manifesto is based on 12 principles:
1.Customer satisfaction by rapid delivery of useful software
2.Welcome changing requirements, even late in development
3.Working software is delivered frequently (weeks rather than months)
4.Close, daily cooperation between business people and developers
5.Projects are built around motivated individuals, who should be trusted
6.Face-to-face conversation is the best form of communication (co-location)
7.Working software is the principal measure of progress
8.Sustainable development, able to maintain a constant pace
9.Continuous attention to technical excellence and good design
10.Simplicity—the art of maximizing the amount of work not done—is essential
11.Self-organizing teams
12.Regular adaptation to changing circumstances

6. JustAnswer | Ask a question get an answer ASAP
The Agile Manifesto is based on 12 principles:
1.Customer satisfaction by rapid delivery of useful software
2.Welcome changing requirements, even late in development
3.Working software is delivered frequently (weeks rather than months)
4.Close, daily cooperation between business people and developers
5.Projects are built around motivated individuals, who should be trusted
6.Face-to-face conversation is the best form of communication (co-location)
7.Working software is the principal measure of progress
8.Sustainable development, able to maintain a constant pace
9.Continuous attention to technical excellence and good design
10.Simplicity—the art of maximizing the amount of work not done—is essential
11.Self-organizing teams
12.Regular adaptation to changing circumstances

7. JustAnswer | Ask a question get an answer ASAP
The Agile Manifesto is based on 12 principles:
1.Customer satisfaction by rapid delivery of useful software
2.Welcome changing requirements, even late in development
3.Working software is delivered frequently (weeks rather than months)
4.Close, daily cooperation between business people and developers
5.Projects are built around motivated individuals, who should be trusted
6.Face-to-face conversation is the best form of communication (co-location)
7.Working software is the principal measure of progress
8.Sustainable development, able to maintain a constant pace
9.Continuous attention to technical excellence and good design
10.Simplicity—the art of maximizing the amount of work not done—is essential
11.Self-organizing teams
12.Regular adaptation to changing circumstances

8. JustAnswer 2003-2014
JustAnswer | Ask a question get an answer ASAP

9. JustAnswer 2003-2014
JustAnswer | Ask a question get an answer ASAP

10. JustAnswer | Ask a question get an answer ASAP
Scrum is about managing teams
LEAN is about
managing products

11. JustAnswer | Ask a question get an answer ASAP
LEAN

12. Ideas
JustAnswer | Ask a question get an answer ASAP

13. JustAnswer | Ask a question get an answer ASAP
Converting your ideas to User Stories
Who is your target audience?
What are you going to provide?
Where this makes sense?
When this makes sense?
Why might this idea work?

14. JustAnswer | Ask a question get an answer ASAP
You should be specific and concrete

15. JustAnswer | Ask a question get an answer ASAP
We did A/B Testing
for a long time..

16. JustAnswer | Ask a question get an answer ASAP
New controls..

17. JustAnswer | Ask a question get an answer ASAP
New pages..

18. JustAnswer | Ask a question get an answer ASAP
Flat design?
Why not!

19. JustAnswer | Ask a question get an answer ASAP
Ability to experiment
is like a super power!

20. It was a nightmare when
we first time saw site on mobile!
JustAnswer | Ask a question get an answer ASAP

21. It was a good time when we
switched to responsive design..
JustAnswer | Ask a question get an answer ASAP

22. We did a lot of tests
for improving engagement
JustAnswer | Ask a question get an answer ASAP

23. JustAnswer | Ask a question get an answer ASAP
Experimenting with
performance..

24. We tested a lot of things
without extra efforts and defects!
JustAnswer | Ask a question get an answer ASAP

25. With Optimizely we kept code clean.
Revizely is our in house tool to replace it.
JustAnswer | Ask a question get an answer ASAP

26. JustAnswer | Ask a question get an answer ASAP
A/B Testing

27. JustAnswer | Ask a question get an answer ASAP
Data

28. Data-Driven: Acceptance Criteria, Requirements, Definition of Done
Who might be interested in data?
Ops, Stakeholders, CEO, VP, PO, BI, Analytics, Developers, QA
Goals, Conversions, CTAs, Micro-Conversions, Navigation, Measured Activity
Client vs. Server, GA vs. CSRT vs. Event Sentry vs. NCV vs. Pixels
Goals, Metrics, Linked References, Performance, Errors, Tests
JustAnswer | Ask a question get an answer ASAP
What data should we collect?
Where data should be sent?
When it is enough data?
Why validate collected data?
Referenced API or Data might be broken, same as your code.. after somebody has changed it

29. Actions States Transitions
JustAnswer | Ask a question get an answer ASAP
Activity Tracking
button clicked
question posted
popup visible
validation error
asked question
after click on logo

30. Data collection: Google Analytics vs Big Data
JustAnswer | Ask a question get an answer ASAP
GA
Premium Universal Google
Analytics
Big Data
In-house Hadoop
Data Base
Back-End API Measurement Protocol Outcome Events
Front-End API YES YES
Navigation Tracking YES YES
Event Tracking YES YES
Standard Reports Yes Limited
Custom Reports Yes Request
SQL Queries Big Query YES
17

31. Data Collection
JustAnswer | Ask a question get an answer ASAP

32. Data Collection
JustAnswer | Ask a question get an answer ASAP

33. Su-Ha-Ri for Data: Su - discuss, validate, validate, repeat
JustAnswer | Ask a question get an answer ASAP
Use
Vocabulary
• Do not call
same things
differently
• Do not use
same term for
different things
Introduce
monitoring
• Integration
and Unit Tests
• Reports
• Alerts
Keep it
Raw
• Avoid
changing
original data
if it is collected
• Avoid data
changes after
it was saved
Include
References
• Avoid
duplicated
data collection
• Collect data
with references
on relevant
objects
19
1 2 3 4

34. Data Monitoring
JustAnswer | Ask a question get an answer ASAP

35. UDniavtears aMl Goonoigtoler Ainnaglytics
JustAnswer | Ask a question get an answer ASAP

36. CDreaattinag Ma doanshibtooarridn tagkes hours
JustAnswer | Ask a question get an answer ASAP

37. Real-Time data from the box!
JustAnswer | Ask a question get an answer ASAP

38. Data-Driven Company
JustAnswer | Ask a question get an answer ASAP
2014 Strategic Priorities

39. As we see the future
JustAnswer | Ask a question get an answer ASAP

40. JustAnswer | Ask a question get an answer ASAP
HEADLINE

41. http://www.justanswer.com/
JustAnswer | Ask a question get an answer ASAP

42. JustAnswer | Ask a question get an answer ASAP