Extreme Programming 2018 — Agile Beyond Scrum

Nelkinda Software Craft Pvt. Ltd.
Extreme Programming
2018
Agile Beyond Scrum
Christian Hujer, CEO Nelkinda Software Craft

Scrum ≠ Agile

Scrum ⊂ Agile

The Two Values of Software

Secondary Value of Software
“The secondary value of Software is its behavior: That it does what the current users
currently need without any bugs, crashes, or delays.”
— Robert C. Martin
⇒ But Users and their needs change over time!

Primary Value of Software
“The ability of software to tolerate and facilitate such ongoing change is the primary value
of software. The primary value of software is that it’s soft.”
— Robert C. Martin

Scrum addresses which of the Two Values?
Scrum addresses the Secondary Value of Software.
Scrum ignores the Primary Value of Software.
It assumes that the Primary Value of Software can be utilized.
But it does not contribute anything to the Primary Value of Software.

What is Scrum?
Let’s Recap!

What is Scrum?
● 3 Roles
○ Product Owner
○ Scrum Master
○ Team Member
● 5-6 Ceremonies
○ Sprint
○ Planning
○ Daily Standup
○ Review
○ Retrospective
○ Backlog Refinement (FKA
● Artifacts
○ Product Backlog Item
○ Product Backlog
○ Sprint Backlog
○ Potentially Shippable Product Increment
● Documentation
○ Definition of Ready
○ Definition of Done
○ Team Charter

Scrum as a Pipeline

What is Scrum?
● Process Framework
⇒ Frameworks are incomplete!
There’s a lot of stuff that Scrum doesn’t tell you!
Are we here for Scrum, or are we here for Agile?
What’s the purpose?

Nelkinda Software Craft Pvt. Ltd.Nelkinda Software Craft Pvt. Ltd.
Manifesto for Agile Software Development
“We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.”
— Agile Manifesto

Principles behind the Agile Manifesto
Who invited to the famous Snowbird meeting?
Robert C. Martin

1st Agile Principle
“Our highest priority is to satisfy the customer through early and continuous delivery of
valuable software.”
— Principles behind the Agile Manifesto
What does Scrum say about this?
“Potentially Shippable Product Increment at the end of every Sprint.”
But, how early can you ship?
And what does Continuous Delivery really mean?
XP: Continuous Integration/Delivery/Deployment

2nd Agile Principle
“Welcome changing requirements, even late in development. Agile processes harness
change for the customer’s competitive advantage.”
How does Scrum deal with that?
What if there is a change request on the last day of the Sprint?

3rd Agile Principle
“Deliver working software frequently, from a couple of weeks to a couple of months, with
a preference to the shorter timescale.”
“Potentially Shippable Product Increment at the end of every Sprint.”
But, how often can you ship?
XP: Ship continuously

4th Agile Principle
“Business people and developers must work together daily throughout the project.”
Is your Product Owner available?

5th Agile Principle
“Build projects around motivated individuals. Give them the environment and support they
need, and trust them to get the job done.”

6th Agile Principle
“The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.”
Is your team co-located?
Does that include the Product Owner?!

7th Agile Principle
“Working software is the primary measure of progress.”
Do you have design sprints? Test sprints?
You shouldn’t!

8th Agile Principle
“Agile processes promote sustainable development. The sponsors, developers, and users
should be able to maintain a constant pace indefinitely.”
What does Scrum call an Iteration?
“Sprint” — WAT?! How can you achieve a sustainable pace with Sprints?
XP: Iteration

9th Agile Principle
“Continuous Attention to technical excellence and good design enhances agility.”
How does Scrum deal with Technical Excellence?
It doesn’t!
XP: Collective Code Ownership, Continuous Integration/Delivery/Deployment,
Continuous Refactoring/Design Improvement, Test-Driven Development,
Acceptance Testing, Pair Programming

10th Agile Principle
“Simplicity--the art of maximizing the amount of work not done--is essential.”
How does Scrum address that?
XP: Simplicity is one of its core values.

“The best architectures, requirements, and designs emerge from self-organizing teams.”
How self-organizing are your teams?
How self-organizing can teams with dedicated responsibilities (QA, BA, DO) be?

“At regular intervals, the team reflects on how to become more effective, then tunes and
adjusts its behavior accordingly.”
“Retrospective”
The most important ceremony in Scrum!

Manifesto for Software Craftsmanship
“As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and
helping others learn the craft. Through this work we have come to value:
Not only working software, but also well-crafted software
Not only responding to change, but also steadily adding value
Not only individuals and interactions, but also a community of professionals
Not only customer collaboration, but also productive partnerships
That is, in pursuit of the items on the left we have found the items on the right to be indispensable.”
— Manifesto for Software Craftsmanship

What comes first?
● Technical Agility?
● Management Agility?
Discuss!
⇒ Technical Agility comes first! Because, Management Agility depends on
Technical Agility, not the other way round!

Values
● Communication
● Simplicity
● Feedback
● Courage
● Respect

To become truly Agile
● Forget about Scrum, maybe.
● Greenfield: Release to production on the first day, automated!
● Brownfield: Reduce release cycles.
● Automate everything. Especially testing and deployment!
There is no such thing as manual testing!
The only manual in testing is exploration!
Do not deploy manually!

What is DevOps?
“Complete definition of DEVOPS: the developers have to wear the beeper.”
— Ron Jeffries on Twitter
What does the Dev in DevOps stand for?
If you have a separate team for DevOps, they’re actually Ops, not DevOps.

Summary
Scrum is a Framework. A lot of Agile Principles are not addressed by Scrum!
Scrum doesn’t tell you anything about the most important part, which is how to
turn requirements into valuable software and put them in production!
XP (Extreme Programming) includes Scrum, but tells you all the practices as well!
Thank you!

Extreme Programming 2018 — Agile Beyond Scrum

More Related Content

Similar to Extreme Programming 2018 — Agile Beyond Scrum (20)

More from Christian Hujer (7)

Recently uploaded (20)

Extreme Programming 2018 — Agile Beyond Scrum

Editor's Notes