+ All Categories
Home > Internet > Process Hacking With Rangle Flow

Process Hacking With Rangle Flow

Date post: 15-Apr-2017
Category:
Upload: fitc
View: 105 times
Download: 2 times
Share this document with a friend
25
Process Hacking with Rangle Flow October 4, 2016 Yuri Takhteyev CTO
Transcript
Page 1: Process Hacking With Rangle Flow

Process Hacking with Rangle FlowOctober 4, 2016 Yuri Takhteyev

CTO

Page 2: Process Hacking With Rangle Flow

“Come for JavaScript, stay for the process.”

Page 3: Process Hacking With Rangle Flow

Define

Prepare

Execute

Why Agile?

Doing Scrum by the Book

Adjustments

Page 4: Process Hacking With Rangle Flow

Why Agile?

Page 5: Process Hacking With Rangle Flow

Define

Prepare

Execute

Three Modes

WaterfallChaos

Agile

Page 6: Process Hacking With Rangle Flow

Define

Prepare

Execute

The Key Idea

Reducing waste

by only building what we actually need

and by limiting work in progress.

Page 7: Process Hacking With Rangle Flow

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 itbut often just makes things worse.

Page 8: Process Hacking With Rangle Flow

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.

Page 9: Process Hacking With Rangle Flow

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.

Page 10: Process Hacking With Rangle Flow

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.

Page 11: Process Hacking With Rangle Flow

Scrum by the Book

Page 12: Process Hacking With Rangle Flow

This is the book.

(Though, there are other good ones.)

Page 13: Process Hacking With Rangle Flow

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.

Page 14: Process Hacking With Rangle Flow

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.

Page 15: Process Hacking With Rangle Flow

Adjustments

Page 16: Process Hacking With Rangle Flow

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?”

Page 17: Process Hacking With Rangle Flow

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.

Page 18: Process Hacking With Rangle Flow

Define

Prepare

Execute

Handling PO’s Commitments

‣“We need all of this.”

‣Handling scope discovery.

‣Building trust.

Page 19: Process Hacking With Rangle Flow

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.

‣http://bit.ly/yuri-cd-2015

Page 20: Process Hacking With Rangle Flow

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.

Page 21: Process Hacking With Rangle Flow

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.

Page 22: Process Hacking With Rangle Flow

Define

Prepare

Execute

Lean UX

‣Dealing with prior design.

‣Talking to the users – ideally, within the sprint.

‣Leveraging analytics.

Page 23: Process Hacking With Rangle Flow

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.

Page 24: Process Hacking With Rangle Flow

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.

Page 25: Process Hacking With Rangle Flow

@qaramazov @rangleio

October 4, 2016 Yuri TakhteyevCTO

Process Hackingwith Rangle Flow


Recommended