How to manage fast-moving projects using Sprint-based and Behaviour-Driven development.

1. The Uncertainty Principle
How to manage fast-moving, projects, clients and
requirements

2. Hello! it’s
about
!
Developer, Problem solver, Ruby
evangelist, Agile practitioner.
You can find me at:
● FredAtBootstrap
● http://bootstrap.me.uk
Fred

3. Chances of failure
https://www.wrike.com/blog/complete-collection-project-management-statistics-2015/
Small Projects
(< $1,000,000)

4. Chances of failure
https://www.wrike.com/blog/complete-collection-project-management-statistics-2015/
Large Projects
(> $1,000,000)

5. 1. Changing priorities within organization – 40%
2. Inaccurate requirements – 38%
3. Change in project objectives – 35%
4. Undefined risks/opportunities – 30%
5. Poor communication – 30%
6. Undefined project goals – 30%https://www.wrike.com/blog/complete-collection-project-management-statistics-2015/
Causes of failure

6. Heisenberg
complementary variables

7. The uncertainty principle (quantum mechanics)

8. The uncertainty principle (software mechanics)
𝚫q
𝚫t
minimise

9. Your Client
I have a great
new idea!!

10. HONESTY
Response #1

11. CUSHIONING
Response #2

12. SCRUM

13. SCRUM lifecycle
(2 weeks)

14. What’s in a Sprint?

15. PRAGMATISM
Response #3

16. Benefits of Sprint-based development
Transparency
Predictability
Reliability
Responsiveness
Risk Mitigation (for customers and self)

17. Difficulties of Sprint-based development
Customers must participate
Works best for small-medium organizations

18. Behavior-Driven
Development Common language +
Executable Specifications

19. Inside-Out development (traditional)
Development
Testing
Stakeholders
Bug
CodeCode
Bug

20. Outside-In development (BDD)
Development
Testing
Stakeholders
FeaturesExecutable specificationsCode

21. BDD Tools

22. Features
Created by: Client / Product
Owner
As an [Actor]
I want [specific System Behavior]
So that I can [have a tangible
benefit]
BDD
Scenarios
Given [a condition exists]
When [an action occurs]
Then [expected result]

23. Feature: User Authentication
As a registered customer
I want to log on the site
So that I can buy some cool stuff
Only custom authentication supported at this stage
If customer has bought during last month show welcome message
If customer hasn’t bought in last month or more, show offers page
Scenario: recent customer logs in
Given customer visits our login page
And customer enters correct username and password
And customer has bought something during last month
Then customer sees “Hi <name>, welcome back!” Message

24. Step definitions
Created by: Developers /
Testers
Feature Scenario
Given [a condition exists]
When [an action occurs]
Then [expected result]
Step Definition
[code that checks condition]
[code that implements action]
[code that tests for expected
result]
BDD

25. Step definitions: User Authentication
Given (/^customer visits our login page$/) do
visit(‘http://our-site.com’)
end
And (/^customer enters correct username and password$/) do
fill_in(usr_name_field, with: ‘fred@gmail.com’
fill_in(password_field, with: ‘password’
end
And (/^customer has bought something during last month$/) do
purchase = Purchases.where(purchase_contact = @user.email)
assert purchase.order_date > Time.now - 1.month
end
And (/^customer sees “Hi <name>, welcome back!” Message$/) do
assert_equal page.has_text?("1 Items found"), true
end

27. Implementation
Created by: Developers
def create
@pid = params[:pid]
@profile = Profile.find_or_create(@pid)
@profile.apply_permissions(current_user)
if params.has_key?(:files)
create_from_upload(params)
elsif params.has_key?(:profile)
add_metadata(params[:profile], "")
end
end
def update
@pid = params[:pid]
redirect_field = ""
if params.has_key?(:redirect_field)
redirect_field = params[:redirect_field]
end
if params.has_key?(:files)
create_from_upload(params)
elsif profile_params
add_metadata(params[:profile], redirect_field)
else
respond_to do |format|
format.html { render action: 'edit' }
format.json { render json: @profile.errors, status:
:unprocessable_entity }
end
end
end
BDD

30. BDD benefits
•Everyone talks the same language
•Expectations are fully understood
•Living documentation
•Measurable progress
•Considerable bug reduction

31. 30% bugs per cycle to 2%
http://www.belatrixsf.com/index.php
/whitepapers-successful-project-
with-behavior-driven-development
BDD benefits: case studies
Zero known defects
http://www.capita-
itps.co.uk/media/127798/BDD-Case-
study-2.pdf

32. SCRUM lifecycle
(2 weeks)

33. BDD Sprint (preparation)
Product backlog
Feature
Scenarios
Knowledge
acquisition
BugsTechnical
work

34. BDD Sprint (2-week cycle)
Day Activity Input Output
1 Planning Product Backlog Sprint Backlog,
Sprint Goal
Client: Sets business priorities
Product Owner + Dev Team: Set technical priorities, estimate work

35. BDD Sprint (2-week cycle)
Day Activity Input Output
1 Planning Product Backlog Sprint Backlog,
Sprint Goal
2-3 Design &
Architecture
Sprint Backlog Step Definitions /
tests
Dev Team: Use Step Definitions to debate and influence design & architecture

36. BDD Sprint (2-week cycle)
Day Activity Input Output
1 Planning Product Backlog Sprint Backlog,
Sprint Goal
2-3 Design &
Architecture
Sprint Backlog Step definitions /
tests
4-9 Coding Step definitions /
tests
<Working Code>
Dev Team: Done = Cucumber green!

37. BDD Sprint (2-week cycle)
Day Activity Input Output
1 Planning Product Backlog Sprint Backlog,
Sprint Goal
2-3 Design &
Architecture
Sprint Backlog Step definitions /
tests
4-9 Coding Step definitions /
tests
<Working Code>
10 Show & Tell <Working Code> Customer feedback
Everyone: show what we’ve done

38. BDD Sprint (2-week cycle)
Day Activity Input Output
1 Planning Product Backlog Sprint Backlog,
Sprint Goal
2-3 Design &
Architecture
Sprint Backlog Step definitions /
tests
4-9 Coding Step definitions /
tests
<Working Code>
10 Show & Tell <Working Code> Customer feedback
10 Sprint Review Pos / neg feedback Improvement list
Dev Team: what we learned

39. 1. Changing priorities within organization – 40%
2. Inaccurate requirements – 38%
3. Change in project objectives – 35%
4. Undefined risks/opportunities – 30%
5. Poor communication – 30%
6. Undefined project goals – 30%https://www.wrike.com/blog/complete-collection-project-management-statistics-2015/
Causes of failure - addressed by Sprint-based BDD

40. Sprints + BDD = Delivering the right software at the
right time!

41. Recommended reading

42. Any questions?
Ping me at:
FredAtBootstrap
fred@bootstrap.me.uk