2014/09/03: Flowcon Day 1

by Gene Kim on

#flowcon

Up: Dianne Marsh, Director of Engineering, Neflix: "Introducing Change While Preserving Engineering Velocity"

  • .@dmarsh: "My promise: I'll tell you about things we could have done better -- unlike how we tend to tell stories on stage" :)
  • .@dmarsh: "Engr Tools Charter: Build the tools that support engr teams' innovation; enable velocity through innovation"
  • .@dmarsh: "we dno't build, bake or deploy for teams; nor do we manage their configs; we build tools to enable self-service"
  • .@dmarsh: "it's important that people don't become dependent upon us"
  • .@dmarsh: "planned 2014 migrations; Centos > Ubuntu AMI; CBF to nebular/gradle; upgrade continuous delivery solns; perforce > git
  • .@dmarsh: "
  • @utahkay: .@dmarsh Introducing change while preserving engineering velocity #flowcon http://t.co/dqoisasp9V
  • .@dmarsh: "migrations are important; b/c we want to move things forward;
  • .@dmarsh: "a big 2014 goal: get all tools out of data center; why? so everyone can innovate like our core cloud service
  • .@dmarsh: "our team are experts at build tools; no top-down command/control; instead, we need to make our tools attractive
  • .@dmarsh: "we manage by context, not control; get context from other teams to inform our roadmap
  • .@dmarsh: "with freedom comes responsibility
  • .@dmarsh: "Define the paved road: broadcast the version ctrl, OS builds, & other tools we've committed to support in future
  • .@dmarsh: "Support Velocity; Customer Engagement Team; from consulting world; hired team doing Dev; stayed away from project managers; didn't have to get permission; at Netflix, we're autonomous; we know what's best for our org
  • Again, listening to @dmarsh, I'm amazed how command & control has been vanquished at Netflix; coming to enterprises, too
  • .@dmarsh: "Embed CET on Tools Development; to ensure that they understood customer needs
  • .@dmarsh: "tool migration goals; engage w/our customers; share the cost of change; encourage self-sufficiency
  • .@dmarsh: "broadly socialize the why: repeatability, business agility: visibility, reliability, speed, simplicity, core competencies
  • .@dmarsh: "selling perforce > git: benefits of distributed version control; & dramatic build time reductions (!!)
    https://pbs.twimg.com/media/BwotxATCYAEfC62.jpg
  • .@dmarsh: "put dates out there, otherwise it won't happen
  • .@dmarsh: "many teams needed more time to get out of data center; nothing bad will happen if we miss the 2014 date
  • .@dmarsh: "Biggest challenge at Netflix: # of teams; requires roadshow (vs merely publishing roadmap); missed all the UI teams
  • .@dmarsh: "teams are on specctrum; some teams well staffed; others haven't been able to staff up, so are bare bones
  • .@dmarsh: "build tooling to support migration; deprecation messages belong in the tool: "what, you're deprecating jenkins?"
  • .@dmarsh: "migration status: SCM 65% complete; build: 50% complete; the remainder are the late majority. Will be big challenge to push this thru
  • .@dmarsh: "To improve: more outreach (so I wouldn't miss the UI teams); Orient (vs Other Teams for social norms); custom training for custom solutions (git) and Google for the rest; hired too slowly
  • .@dmarsh: "I have 22 people on my team; 6 on ??, 8 on Build Tools, new Dev Tool team (stash, artifactory, etc), 4 on CET
  • Another insight listening to @royrapoport & @dmarsh: despite extent of team autonomy & anti-command/control, lots of reliance on people wranglers (managers)
  • .@dmarsh: "Your Freedom can't be my Responsibility" (har har)
  • @mikagrml: "Netflix Culture: Freedom & Responsibility" slide deck: http://t.co/jgIPeEqGR9
  • .@dmarsh: "how do we gauge success of migration?

Andrew Malcom

  • Malcom: "Nintendo Wii peaked in 2007; they built amazing value, but haven't sustained (even vz worst biz in world: Comcast)
  • Malcolm: amazing graph of Nintendo market cap (peak in 2007); vs Comcast (har har)
    https://pbs.twimg.com/media/Bwo2GwwCMAASEr2.jpg
  • @bitNomad: the product alone is not enough
  • myspace v facebook
  • plaxo v linkedin need to build the system around it to build a business

note that scrolling region is incorrect -- text only shows up here, and scrolling doesn't work below!

Misc

  • @cbgrasshopper: RT @bitNomad: Henrik Kniberg quoted by @mpoppendieck and now @eriksowa: Alignment is the process of making clear the constraints #flowcon #…
  • @quicola: My #FlowCon slides are up: http://t.co/ZLUSlSFc6i #leanux #teamwork #castells
  • @byronschaller: RT @bitNomad: Henrik Kniberg quoted by @mpoppendieck and now @eriksowa: Alignment is the process of making clear the constraints #flowcon #…
  • @thinknow: RT @FlowConSF: Morning slides are uploaded at our website: http://t.co/PZpcGUKpXJ #FlowCon
  • RT @FlowConSF: Morning slides are uploaded at our website: http://t.co/PZpcGUKpXJ #FlowCon
  • RT @bitNomad: product alone is not enuf
  • myspace v facebook
  • plaxo v linkedin need to build the system around it to build biz
  • Malcolm: "Skype is the largest telco in world; despite not being a great product (it sure was in 2008): 2B call-minutes/day
  • Malcolm: "As the guy who ran revenue at Skype, this was my problem: skype > skype calls were free; we charged for PTSD calls"
  • Malcolm: "we got big bonus if we could hit $300MM revenue;
  • Malcolm: "diff between great products vs great businesses; solve problems that users pay for
  • Malcolm describing difference between great products vs. great businesses:
    https://pbs.twimg.com/media/Bwo3tQPCQAAlfJX.jpg
  • @botchagalupe: RT @jeffsussna: RT @quicola: My #FlowCon slides are up: http://t.co/E9gKCk3ITs #leanux #teamwork #castells << very nice
  • @zacfrank: “How does Skype make money? [SILENCE] As the person who ran revenue at Skype, this was my problem."
  • RT @zacfrank: “How does Skype make money? [SILENCE] As the person who ran revenue at Skype, this was my problem."
  • Malcolm: "there's never been a platform that lasted for more than a decade: eg, AOL IM, ICQ, etc."
  • @SoberBuildEng: TIL: Skype started out as Kazaa

Misc

  • @nohz: RT @cbgrasshopper: Tools don't help much with continuous delivery of systems that aren't architected in a way that lends itself to CD - Sam…
  • @jmeowmeow: RT @utahkay: .@samnewman describing microservices at #flowcon http://t.co/ZgMxT1L3wb
  • @The_Quacker: RT @PeterShanley: Beware flying purple h.i.p.p.o's who poop gold... Even the military abandoned command&control. @BarryOReilly #flowcon htt…
  • @cbgrasshopper: #flowcon is one of the best technology conferences you could participate in. It deserves to be far better attended than it is.
  • @estherderby: Gr8 product, gr8 business Andrew Malcolm #flowcon http://t.co/dQ9ADDREi3
  • @cbgrasshopper: RT @The_Quacker: From Technology is Not Enough, @BarryOReilly the goal is not to create certainty, its to diminish uncertainty #RT @raucousmusing: RT @estherderby: A journey to continuous flow at nordstrom #flowcon http://t.co/Tjbkvrltcf
  • FlowCon
    https://pbs.twimg.com/media/Bwotf9eCYAAGyAx.jpg
  • @raucousmusing: RT @estherderby: A journey to continuous flow at nordstrom #flowcon http://t.co/Tjbkvrltcf
  • @raucousmusing: RT @estherderby: A journey to continuous flow at nordstrom #flowcon http://t.co/Tjbkvrltcf
  • @adrianco: RT @RealGeneKim: .@dmarsh: "Define the paved road: broadcast the version ctrl, OS builds, & other tools we've committed to support in futur…
  • Malcolm: "Cust acquisition via Network Effect is diminishing b/c ??? effects of centralized App Stores"
  • Malcolm: "What Skype could have been: communication suite (like WhatsApp) or Join.Me, as opposed to Group Video route
  • Malcolm: "At skype: If we could have built enterprise features and become join.me; we could have become Google Helpouts
  • Fascinating listening to Malcolm reflect on how Skype could have become even bigger; roadmap chgs, category chgs, etc.
  • Malcolm: "Amazon disadvantaged by not having big cash cow called Search; hard to sustain 1% margins while investing in drones
  • @utahkay: Most valuable tool for an architect: a whiteboard @samnewman
  • @cattsmall: RT @slowbluecamera: “Take initiative and apologize later. Things often don’t look good on paper.” +1! @cattsmall “We’re all Designers” at #…
  • @cattsmall: Thanks to everyone who came to my talk at #flowcon! Death to silos!
  • @abuzzacaro: RT @quicola: My #FlowCon slides are up: http://t.co/ZLUSlSFc6i #leanux #teamwork #castells

DON REINERSTEN

@cattsmall: RT @slowbluecamera: “Take initiative and apologize later. Things often don’t look good on paper.” +1! @cattsmall “We’re all Designers” at #…

  • Reinersten: "topics for today: queueing, batch size reduction, fast feedback, congestion control
  • Reinersten: "Queuing: traffic at rush hour: 4 lanes > 3 lanes: 25% capacity reduction leads to 2x incr cycle time; non linear
  • Reinersten: "This is, of course, an example of M/M/1/infinity queue" (more math in this talk than avg #flowcon talk :)
  • Holy cow. Finally, a definitive source for the % busy/% idle from #PhoenixProject!!! @bmc_devops
    https://pbs.twimg.com/media/Bwo-Pm-CcAECMVT.jpg
  • @utahkay: Our mental models are deterministic, and break down when you reach high utilization in a stochastic system. @DReinertsen

RT @utahkay: Our mental models are deterministic, & break down when you reach high utilization in a stochastic system. @DReinertsen
* .@DReinertsen: "In mfg, queues are visible; in Dev, queues are information and invisible
* .@DReinertsen: "98% of Dev aren't measuring size of queues; only 15% are tracking cost of delays"
* .@DReinertsen: "utilization has higher impact on cycle time (vs variability)
* @bitNomad: in manufacturing, we carry queues on the cost sheet as inventory. In knowledge work, it's RnD as Work in Process in people's heads
* @bitNomad: in manufacturing, we carry queues on the cost sheet as inventory. In knowledge work, it's RnD as Work in Process in people's heads
* RT @bitNomad: in manufacturing, we carry queues on cost sheet as inventory. In knowledge work, it's RnD as WIP in people's heads
* @utahkay: Cost of delay is not as visible as cost of excess capacity @DReinertsen #flowcon http://t.co/zFWroUpQpZ
* @bitNomad: mathematically your leverage on queues is capacity utilization: limit your wip

  • RT @bitNomad: mathematically your leverage on queues is capacity utilization: limit your wip

  • .@DReinertsen: "Ford Harrison first wrote about economic lot size in 1913; involves high school calculus" (!!)

  • (Goldratt: "more papers written on optimal lot size than any other area in manufacturing")

  • .@DReinertsen: "Reducing batch size almost always pays off, if you understand the economics of it"

  • .@DReinertsen: "Fast feedback; queue size is far-leading indicator of cycle time; that's obvious, right?" (nice.)

  • .@DReinertsen: "As you can see, queue size alerts at time 21, cycle time alerts only at time 41"

    https://pbs.twimg.com/media/BwpAp6_CcAAR54x.jpg

  • The concept/word density in this @DReinertsen talk may be higher than any I've ever heard. Wow. Having diff time typing

  • .@DReinertsen: "Flow = Speed x Density";

  • .@DReinertsen: "

  • @AdamYuret: RT @bitNomad: flow efficiency: just b/c you're busy (utilization) doesn't mean you're efficient. In practice companies are around 5% takt t…

  • @AdamYuret: RT @bitNomad: people don't resist change, they resist being changed - Senge quoted by @sarahbeee

  • @bitNomad: the faster you can respond to emergent queues, guaranteed due to variability, the more money you make by not letting them persist

  • @bitNomad: high utilization is a traffic jam on a freeway. what you want is low cycle time (throughput), no queue, and flow

  • .@DReinertsen: "We should add capacity margin in zones of high variation; in highway, add capacity in hills (vs flat land)

  • .@DReinertsen: "Adaptive controls aid flow; eg: red light when no one using green light

  • .@DReinertsen: "Queues produce spontaneous variation

  • .@DReinertsen: "Takeaways: capacity & queues cost $$; know cost of delay (citing Leffingwell); decr batch sz before incr capcity

  • .@DReinertsen: "reducing batch sz by 100x decreases transaction cost by 10x (f(sqrt)); design process to tolerate variability

  • (I feel like I need some remedial

  • OMG. I met @drunkcod! Great quote on @DReinertsen book!

    https://pbs.twimg.com/media/BwpEPEECcAAoZEB.jpg

  • .@DReinertsen: "look for design guidance where we assume we can't change variability

  • .@DReinertsen: "

  • Golly. You could design an entire masters degree curriculum around this 30m @DReinertsen talk.

  • @bitNomad: create processes that work in a world of variation rather than drive it out; plan to compensate when it happens @DReinertsen

  • @adrianco: RT @bitNomad: as you approach mastery, the less you enjoy learning (and the less information you generate)
    @johnsonwhitney

  • @thinknow: Ways to break down silos: Involvement, open meetings, feedback, chats and link sharing, end-to-end teams. @cattsmall

  • @utahkay: Responding quickly to rising queues costs no more than responding late, and saves much more @DReinertsen

  • RT @utahkay: Responding quickly to rising queues costs no more than responding late, and saves much more @DReinertsen

  • @AdamYuret: RT @thinknow: "Shared documents aren't shared understanding" @jeffpatton #flowcon http://t.co/CvsRwgGGy8

  • RT @bitNomad: high utilization is a traffic jam on a freeway. what you want is low cycle time (throughput), no queue, and flow

  • .@DReinertsen: "Flow is unstable, like turbulence in laminar flow; smoothing flow increases throughput"

Whitney Johnson:

  • @bitNomad: service economy: "people don't buy products, they hire products to serve needs. Disruptors look for unmet needs" @johnsonwhitney
  • @bitNomad: service economy: "people don't buy products, they hire products to serve needs. Disruptors look for unmet needs" @johnsonwhitney
  • @adrianco: RT @bitNomad: as you approach mastery, the less you enjoy learning (and the less information you generate) @johnsonwhitney @estherderby: RT @utahkay: S-curve helps us with the psychology of disruption @johnsonwhitney @erik_petersen: #Awesome #agile #lean@eventifierapp @FlowConSF Here's the social media recap for #FlowCon, have a look: http://t.co/6CRfJqDM9B
  • @randbits: RT @slowbluecamera: “Take initiative and apologize later. Things often don’t look good on paper.” +1! @cattsmall “We’re all Designers” at #…
  • @randbits: RT @slowbluecamera: “Take initiative and apologize later. Things often don’t look good on paper.” +1! @cattsmall “We’re all Designers” at #…
  • @utahkay: In other words, disruptors take on market risk rather than competitive risk @johnsonwhitney
  • @aneel: RT @bitNomad: you can't compare cycle time with utilization unless you bring it to the same unit of measure: economics @DReinertsen #flowcon
  • @tereTx: RT @utahkay: .@johnsonwhitney Moved up Wall Street from secretary to investor and company founder. How did she do it? #flowcon http://t.co/
  • @dmarsh: I've attended keynotes at #inc5000 --- Whitney Johnson would be a great speaker for that audience. Thrilled to have her at #flowcon!
  • Johnson: "It's been posited that skateboarders are great innovators; fast and useful feedback" (great #velocityconf keynote this yr)
  • @quicola: For disruptors, constraints are tools rather than obstacles - Whitney Johnson
  • @rainyamosher: #flowcon validated strong product management and solid architecture are keys for tech success. @jezhumble @cagan @samnewman
  • @jbbrown: Our #flowcon slides are up http://t.co/dVbSirASXM @caitlin_warnock @FlowConSF
  • @cbgrasshopper: RT @bitNomad: by limiting your options you make your problem smaller and have more capacity with which to solve it. @johnsonwhitney
  • @cattsmall: Never stop learning. When you master one skill, try something else.
  • Johnson: on breaking the "failing > shame" downward spiral:
    https://pbs.twimg.com/media/BwpSXqLCEAA9Asi.jpg
  • @stbrodie: #flowcon Beware the undertow of the status quo! @johnsonwhitney
  • @cbgrasshopper: RT @utahkay: Decentralized actors can act very effectively in the presence of good centralized information @DReinertsen
  • @eshamow: RT @RealGeneKim: .@DReinertsen: "reducing batch sz by 100x decreases transaction cost by 10x (f(sqrt)); design process to tolerate variabil…

  • @bitNomad: by limiting your options you make your problem smaller and have more capacity with which to solve it. @johnsonwhitney

  • @RealGeneKim: Johnson: "It's been posited that skateboarders are great innovators; fast & useful feedback" (great #velocityconf keynote this yr)

  • @eshamow: RT @RealGeneKim: .@DReinertsen: "Takeaways: capacity & queues cost $$; know cost of delay (citing Leffingwell); decr batch sz before incr c…

  • @eshamow: RT @RealGeneKim: .@DReinertsen: "We should add capacity margin in zones of high variation; in highway, add capacity in hills (vs flat land)…

  • @eshamow: RT @RealGeneKim: .@DReinertsen: "Flow is unstable, like turbulence in laminar flow; smoothing flow increases throughput"

  • @eshamow: RT @RealGeneKim: RT @bitNomad: high utilization is a traffic jam on a freeway. what you want is low cycle time (throughput), no queue, and …

  • @eshamow: RT @RealGeneKim: .@DReinertsen: "Fast feedback; queue size is far-leading indicator of cycle time; that's obvious, right?" (nice.)

  • @eshamow: RT @RealGeneKim: .@DReinertsen: "Reducing batch size almost always pays off, if you understand the economics of it"

  • @bitNomad: lack of constrants on the surface are exhilirating but create a hard to optimize complexity:
    10° of freedom == 2^10 choices 1024

  • @scshepard: RT @bitNomad: buying eggs all in one yearly batch: low transaction cost, high holding cost. buying eggs 1 at a time is inverse. Find the ba…

  • RT @utahkay: Decentralized actors can act very effectively in the presence of good centralized information @DReinertsen

  • Johnson: "recasting measuring peformance: like Moneyball: b/c he looked funny while throwing fastball; 5x higher groundball/non-groundball ratio

  • Johnson: "most important measure of success? how many # did you show up? ex: scholar w/highest # published also submitted most

  • Johnson: "# of trials as winning performance metric is based on Equal Odds Principle"

  • @bitNomad: we all like to make plans for the future, but following a disruptive path means you cannot see the top of the hill (it's emergent)

    flowcon

  • @adrianco: RT @ph1: My takeaway theme for #flowcon today: how do we enable small autonomous teams that still work as a unified collaborative whole.

  • Johnson: "if it feels scary and lonely, you are probably on the right track"

  • Great diagram on mastery from Johnson: also shows the challenge of boundary-spanning

    https://pbs.twimg.com/media/BwpUGD3CYAEGWlz.jpg

  • @adrianco: RT @bitNomad: disruption is by definition scary and lonely, but if you feel that way you're probably on the right track. @johnsonwhitney #f

  • https://pbs.twimg.com/media/BwpT6eJCUAAGite.jpg

  • @tonycollander: RT @gmiranda23: "If you think your job is to gather and document 'requirements'; that's the IT mindset" @cagan

  • @Magnus919: @ph1 @adrianco I've been thinking about this lately (not at #flowcon). Answer? Think of teams like SOA.

  • @utahkay: What the brain craves is the delicious dopamine of the unpredictable @johnsonwhitney

  • @tonycollander: RT @leslieborrell: "at least half the product ideas we have, won't actually work with cutomers" @cagan

  • @quicola: Dreams are the biggest disruptors - Whitney Johnson

Up: Ben Rockwood, Director of Cloud Operations! Feng Shui In the Modern Business World (@benr)

  • On @benr from Esser: "Probably gave one of the first talks on DevOps at the LISA conference 3 years ago!" (A great talk!)
  • .@benr giving kudos to @DReinersten's book; crowd applauds and cheers; haha
  • "Feng Shui == Wind Water; allow Energy (Qi) to Flow" (clever! @benr just ordained self foremost expert on CI/CD/DevOps Feng Shui :)
  • .@benr: "@bitNomad: who is your organization's system administrator? are they operating with the patterns of devops and flow? #flowcon @benr
  • .@benr: "
  • @nohz: The new software cycle. @benr #flowcon http://t.co/TYg8RgAAwQ
  • .@benr: "From LEI: 1) identify value; 2) map value stream; 3) create flow; 4)
  • @bitNomad: (complex) systems thinking: a frog is > the parts it's made of. You can't just take it apart, put it back together, & get the same
  • .@benr musing about a dollar entering org, everyone takes a piece; how does customer get more than a dollar back? (awesome)
  • .@benr: "Pattern 1: start with why; why are we here? intentionality"
  • .@benr on Deming 5 Deadly Diseases: "All this talk on 'pivots' often drives me insane; short-term thinking
    https://pbs.twimg.com/media/BwpaDCSIUAIAj-5.jpg
  • .@benr: "Pattern 2: build trusting relationships; success often relies on people being truthful, telling bad news"
  • .@benr: "Toyota exec: hearing 'there's no problem' is a problem" (haha. haven't heard that before. Love it!)
  • @utahcreative: Success depends on being truthful about failure and challenges.... This requires trust.
  • .@benr: "Conway's Law
  • .@benr: "Senge: in absence of vision and context, we're on unceaseless treadmill of problem-solving; best is absence of problems
  • @nohz: RT @cattsmall: Build trusting relationships with coworkers through one-on-one discussions.
  • @nohz: "No problem is problem" said with Japanese accent. @benr
  • @adamhjk: Right now, @benr is showing the power of real research coupled with deep daily practice. He may be the best of us. #devops
  • .@benr: "Pattern 5: Standardize Work; employees should never struggle on what to do
  • .@benr: "Pattern 6: manage flow in the value stream;
  • .@benr: "Pattern 7: eliminate waste
  • @tereTx: Tech debt is massively overemphasized and overrated. -@benr #flowcon http://t.co/8tlgzn1uYk
  • @bitNomad: visualize the system; get it down on paper, then you can start to have rational conversations about it @benr
  • .@benr: "Pattern 8: kaizen == "change for the better"" (or two characters: "change" "good", as Sam Guckenheimer informed me)
  • @nohz: RT @bitNomad: what are you putting time and energy to that isn't contributing to the value stream? being truthful about it is hard. @benr #…
  • @adamhjk: Seriously - @benr is @allspaw, @jezhumble and @markimbriaco in one talk right now. Self assured, honest, deep knowledge.
  • @bitNomad: too often we go in with the solution before we truly understand the problem - @benr
  • .@benr: "Drucker: efficiency is doing things right; effectiveness is doing the right things"
  • .@benr: @bitNomad: what's important is having an a3 mindset;: you can do an a3 on a wiki. do the root cause analysis and understand the problem @benr
  • .@benr: "More Deming
  • .@benr: "Pattern 9: Jidoka: built in fault detection facilitating fast recovery; ex: idempotent tools
  • .@benr: "
  • @nohz: RT @adamhjk: Never sacrifice the system for a process @benr

  • @BarryOReilly: RT @The_Quacker: From Technology is Not Enough, @BarryOReilly the goal is not to create certainty, its to diminish uncertainty #FlowCon

  • @samnewman: RT @tereTx: Balance testing and monitoring. Testing is not just pre-release. @samnewman #flowcon http://t.co/InfKKdQfDt
  • @JeffEinhorn: RT @jbbrown: Our #flowcon slides are up http://t.co/dVbSirASXM @caitlin_warnock @FlowConSF
  • RT @adamhjk: Right now, @benr is showing power of real research coupled w/deep daily practice. He may be the best of us. #devops RT @nohz: RT @adamhjk: Never sacrifice the system for a process @benr RT @The_Quacker: From Tech is Not Enough, @BarryOReilly goal is not to create certainty, its to diminish uncertainty #FlowCon
  • .@benr: "On why TQM failed" (reflecting on hanging out at manufacturing plant)
  • @trevorghess: That moment when everyone is taking pictures of the slides. #flowcon http://t.co/f6WymJFau8
  • Journal of Management 1962 RT @trevorghess: That moment when everyone is taking pictures of the slides. #flowcon http://t.co/f6WymJFau8
    https://pbs.twimg.com/media/BwpeFUNCAAAKSfU.jpg
  • @adrianco: Summary slide from @benr excellent Feng Shui of Flow keynote at #flowcon http://t.co/XYhs8JdAfE
  • RT @adrianco: Summary slide from @benr excellent Feng Shui of Flow keynote at #flowcon http://t.co/XYhs8JdAfE
  • https://pbs.twimg.com/media/BwpeEK3IgAAfCzL.jpg
  • @shmula: RT @utahkay: Why TQM failed (from a 1982 article). Oh, and I could replace the word TQM with Agile... @benr #flowcon http://t.co/QTN0P24agd
  • RT @utahkay: Why TQM failed (from a 1982 article). Oh, and I could replace the word TQM with Agile... @benr #flowcon http://t.co/QTN0P24agd
  • https://pbs.twimg.com/media/BwpeoBLCMAAZsM8.jpg
  • @lonefreak: "Changing from regular books to audio books is like changing from a pull system to a push system" - @benr Brilliant!!!

Up: Adam Jacob, @adamhjk

  • @cattsmall: Props to @thinknow for pushing her way through laryngitis to help make #flowcon happen today! That is true diligence. THANK YOU, LANE!
  • RT @cattsmall: Props to @thinknow for pushing thru laryngitis to help make #flowcon happen today! That is true diligence. THANK YOU, LANE!
  • @bitNomad: you aren't going to understand what your customers want by only staring at the words they use
  • @mikagrml: Now @adamhjk of #chef fame on stage at #Flowcon http://t.co/vvERa892Bg
  • RT @mikagrml: Now @adamhjk of #chef fame on stage at #Flowcon http://t.co/vvERa892Bg
  • https://pbs.twimg.com/media/Bwpg4ZOCIAAMsqj.jpg
  • @benr: we should take your fave books, record the audiobooks, narrated by Gilbert Godfrey. :)

  • .@adamhjk: "Phil Dibowitz, Facebook: The #1 thing we can't do is get in people's way" (on why anyone at Facebook can deploy anything)

  • @bitNomad: when you fail you can either blame human beings or learn from your mistakes - @adamhjk

    flowcon

  • @BarryOReilly: First unedited printed copies of #LeanEnterprise at #FlowCon. Thanks @OReillyMedia. http://t.co/ABxFASB8wd

  • RT @BarryOReilly: First unedited printed copies of #LeanEnterprise at #FlowCon. Thanks @OReillyMedia. http://t.co/ABxFASB8wd

  • https://pbs.twimg.com/media/BwphrWyCIAAe_Dp.jpg

  • .@adamhjk: "acccountability; just culture; continuous integrate; make failures small; reinforce culture with tooling

  • .@adamhjk: "here's the bad advice I gave you before, which is alll wrong"

    https://pbs.twimg.com/media/Bwpi-t7CMAAfJ8W.jpg

  • @bitNomad: find a safe way to blow it all the way up: confine the blast radius, but don't limit the magnitude of the explosion

  • @bitNomad: it's not enough to show up at #flowcon; you have to change the system to no longer support the old method of operation.

  • .@jezhumble: "Give us feedback at this form: http://bit.ly/flowcon2014"

  • @mrtn_su: Excellent slides from @DReinertsen's @FlowConSF talk "The Logic of Flow: Some Indispensable Concepts" http://t.co/O87r3vciVy #FlowCon

  • @leslieborrell: Organizations that succeed with continuous delivery have cultural allergies to things that make you slow

  • RT @lonefreak: "Changing from regular books to audio books is like changing from pull system to push system" - @benr Brilliant!!!