"Clean Agile" with Bob Martin (uncle Bob)

 I listened to an O'Reilly Live Event with Bob Martin

https://learning.oreilly.com/accounts/login-check/?next=/live-training/courses/-/0636920061744/

Bob was one of the original signatories of the Agile Manifesto, a software legend and no holds barred educator.


key takeaways

  • Agile does not make you go faster, it produces data to understand where the project is at
    • We do Agile to get data such as velocity and burndown, "to see how screwed we are"
    • We want the bad news as early as possible, cold hard data
    • So we can react and adjust our definition for: fast, cheap, good, done (for the feature/project)
    • Agile is about managing a successful outcome given all your constraints
  • Agile software development at 30k foot level is dividing project up into small time increments, measuring how much you get done, multiplying out to get a date and making adjustments as necessary given your constraints e.g. we want to launch X 



my notes

Agile is a set of disciplines

Product Owner is chief specificer, has the problem, specifies the features of the system

Project Mgr handles schedules, cost. Not defining features

How do you manage a software project?

  •   badly, hope & prayer, fear and motivation

Mismanagement leads to: producing wrong product, inferior quality, being late, 80 hours a week

Pick any 3 of good, fast, cheap and done. You can't get all 4 simultaneously.

  • So you have to quantify "how good?", "how fast?", "how cheap?"  (schedule, scope, quality, staff)
  • Product Manager/Owner are supposed to manage the project to the best possible outcome by managing these factors
  • To do this you need data
    • teams velocity is useful data
    • how much work (story points) remain is useful data
    • note: there are going to be changes, estimates will change, more tasks added/removed

  

  • We do Agile to get these 2 charts on the wall, "to see how screwed we are"
    • Agile does not make you go faster, it produces data to understand where the project is at
    • We want the bad news as early as possible, cold hard data


In software the dates are often frozen but the specs are not. Agile is about managing a successful outcome

Agile: 

  • Exploration and Coding happen at the same time (tho more analysis & design @ start than end)
  • You split the timeline into timeframes e.g. weeks (or 2 week sprints)
  • You build out slices, verticals, which includes UI, middleware and BE
  • Goal: don't half do a feature, do complete features even if only half
  • After a couple of sprints you have enough data to understand if the project is doable or not in expected timeframe



Comments

Post a Comment

Popular posts from this blog

My Reading Lists

I had some time over Christmas and decided to organize my reading lists. Interesting how some time away from daily work allows one to raise up your head   Uncle Bob on Principles of OOd See also book: Agile Principles, Patterns, and Practices in C# Available on Safari Books online. Algorithms in a Nutshell Nine   Algorithms   That Changed   the Future Programming Pearls book: http://www.cs.bell-labs.com/cm/cs/pearls/toc.html 97 Things Every Programmer Should Know Seven L a nguages http://pragprog.com/book/btlang/seven-languages-in-seven-weeks Codys book : http://www.domenlightenment.com/ Principles of OO programming: http://www.nczonline.net/blog/2012/12/18/now-available-principles-of-object-oriented-programming-in-javascript-beta/ Object Oriented programming with Stefan Stoy... Chrome V8 : http://code.google.com/p/v8/ https://developers.google.com/v8/ https://developers.google.com/v8/design - read this Mozilla Javascript page ...
Read more

angular js protractor e2e cheatsheet

Many from the protractor test suite category detailed task syntax example load page load a page browser.get('yoururl') browser btn actions browser back/forward browser.navigate().back() OR browser.navigate().forward() access elements on page See Protractor API list and examples from Protractors test suite access by angular ngmodel name (must match ngmodel in the html) this is the preferred approach element(by.model('person.name')); access by the css id on the page e.g, #user_name (but this can be brittle) element(by.id('user_name')) access angular binding to get generated value i.e. for {{}} element(by.binding('person.concatName')); access angular repeat list data (must match repeat stmt in the html) See Protractor test suit l...
Read more

react-select stacking order bug, z-index, layers and stacking

Image
Had to fix a tricky bug related to react-select recently (our Dropdown component wraps react-select). Here's the how the bug manifested. Dropdown does not overlay dynamically added content below it Variations of this have been reported since 2017. But I tried all the suggestions in the comments and none worked for me. I also tried wrapping the Dropdown in a div and changing z-index to be higher as well as making absolute position but no success. Changing the elements order in the html source and then reordering using flexbox order does work but it breaks the tabbing flow and is not recommended from an accessibility standpoint. One issue is the Dropdown is in a container and is constrained by the containers z-index. No matter how I change the Dropdowns z-index, its container is stacked below the next in stacking order. Google Chrome debugger layers tool provides a cool way to visualize layers. Could be better but helps, check it out below. You have to look closely but you can see h...
Read more