Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Process Hacking With Rangle Flow


Published on

Presented at Web Unleashed 2016
with Yuri Takhteyev,

FITC produces events for digital creators in Toronto, Amsterdam, NYC and beyond
Save 10% off any of our events with discount code 'slideshare'
Check out our events at
or follow us at

Following a good process can make a huge difference for a success of a software project. At we have had an lucky opportunity to refine our approach to software delivery by applying it to a large number of projects over the last three years. In this talk I will share our experiences and describe the process that we have arrived on, which is based on Scrum, continuous delivery, agile testing, and lean UX.


To share’s experiences in developing our software delivery process.

Target Audience

Managers, scrum masters, developers, testers, UX designers.

Assumed Audience Knowledge

General familiarity with the common challenges experienced in the process of building software.

Five Things Audience Members Will Learn

Why continuous delivery is key
How Scrum supports continuous delivery
The role of good git practices
How to approaching testing in an agile process
How to integrate UX design with Scrum

Published in: Internet
  • Be the first to comment

  • Be the first to like this

Process Hacking With Rangle Flow

  1. 1. Process Hacking with Rangle Flow October 4, 2016 Yuri Takhteyev
  2. 2. “Come for JavaScript, stay for the process.”
  3. 3. Define Prepare Execute Why Agile? Doing Scrum by the Book Adjustments
  4. 4. Why Agile?
  5. 5. Define Prepare Execute Three Modes Waterfall Chaos Agile
  6. 6. Define Prepare Execute The Key Idea Reducing waste by only building what we actually need and by limiting work in progress.
  7. 7. Define Prepare Execute Why Would We Build Things We Don’t Need? ‣Developers don’t know what the users need. ‣Product managers don’t know what the users need. ‣User’s don’t necessarily know what they need either. Waterfall process attempts to fix it but often just makes things worse.
  8. 8. Define Prepare Execute How Do We Solve This? ‣Value and feedback through “early and continuous delivery of valuable software” (Agile Manifesto Principles). ‣Close collaboration through self-managing teams.
  9. 9. Define Prepare Execute What’s Wrong with Work in Progress? ‣You aren’t getting value from WIP. ‣You don’t know if you ever will. ‣Context switching destroys productivity.
  10. 10. Define Prepare Execute How Do We Avoid Work in Progress? ‣Break up the work. (Then break it up some more.) ‣Finish what you started before moving on.
  11. 11. Scrum by the Book
  12. 12. This is the book. (Though, there are other good ones.)
  13. 13. Define Prepare Execute Why Scrum? ‣“An ideal balance between abstract principles and concrete practices” (Large-Scale Scrum by Larman & Vodde). ‣This makes it a great place to start. (Consider kanban later.) ‣Scrum is not meant to be dogmatic: it should be adapted based on your learning. ‣But people start cherry-picking too quickly. So they maintain the status quo under a new name. Give proper Scrum a chance before experimenting.
  14. 14. Define Prepare Execute Key Practices ‣The team: a Scrum Master, a Product Owner, and team members. ‣A prioritized backlog of “user stories”. ‣Timeboxing through short “sprints” that lead to shippable software. ‣Scrum ceremonies. ‣Retrospectives.
  15. 15. Adjustments
  16. 16. Define Prepare Execute The Importance of Prioritizing ‣This is the heart of Scrum. ‣“What would we work on if this was the last sprint?” ‣“Can we ship it? Why not?”
  17. 17. Define Prepare Execute Working with the Product Owner ‣In the context of professional services, the PO is usually new to Scrum. ‣You need the right person. ‣Much of our Scrum Master’s work is working the PO. ‣This requires flexible arrangements.
  18. 18. Define Prepare Execute Handling PO’s Commitments ‣“We need all of this.” ‣Handling scope discovery. ‣Building trust.
  19. 19. Define Prepare Execute Continuous Delivery ‣Working software reduces uncertainty and builds trust. ‣Continuous integration to keep working software working. ‣Proper Git workflow: reviewed pull requests. ‣Continuous deployment. ‣
  20. 20. Define Prepare Execute What Happens to QA? ‣If you do Scrum by the book, there are no roles. ‣But there are people who understand quality. ‣Bring them in early. Focus on preventing defects. ‣Do testing within the sprint. Better yet, within the pull request.
  21. 21. Define Prepare Execute The Project Kickoff ‣We want to start a new project quickly, but there is lack of common ground. ‣(Sometimes not even between the different people on the client’s team.) ‣Enter Clarity Canvas, a specific process for establishing common understanding. (See Mike Costanzo’s talk from yesterday.) ‣Limit it to a couple of days.
  22. 22. Define Prepare Execute Lean UX ‣Dealing with prior design. ‣Talking to the users – ideally, within the sprint. ‣Leveraging analytics.
  23. 23. Define Prepare Execute A Rose by Other Name: Process Hacking ‣Everybody does Scrum today. Nobody does Scrum today. ‣Everybody does something they call “Scrum”. ‣Be creative about terms and selling points. Focus on principles and benefits.
  24. 24. Define Prepare Execute From Agile Teams to Agile Organization ‣The same principles work for managing your organization. ‣We tend to use kanban for internal projects.
  25. 25. @qaramazov @rangleio October 4, 2016 Yuri Takhteyev
 CTO Process Hacking
 with Rangle Flow