agile   72474

« earlier    

An epic treatise on scheduling, bug tracking, and triage - apenwarr
Many projects have poorly defined (and often overridden) priorities, hopelessly optimistic schedules, and overflowing bug trackers that are occasionally purged out of frustration in a mysterious process called "bug bankruptcy." But a few projects seem to get everything right. What's the difference? Avery collected the best advice from the best-running teams at Google, then tried to break down why that advice works—using math, psychology, an ad-hoc engineer simulator (SimSWE), and pages torn out of Agile Project Management textbooks.

We'll answer questions like:
Why are my estimates always too optimistic, no matter how pessimistic I make them?
How many engineers have to come to the project planning meetings?
Why do people work on tasks that aren't on the schedule?
What do I do when new bugs are filed faster than I can fix them?
Should I make one release with two features or two releases with one new feature each?
If my bug tracker is already a hopeless mess, how can I clean it up without going crazy or declaring bankruptcy?

Once upon a time, Avery was the lead engineer for Google Fiber's home wifi devices, building, managing, and monitoring the whole fleet in customers' homes. More recently, he's branched out into projects that are harder to explain. Before that, he started startups including one that deployed Lotus Domino in 10 minutes, and one that did unspeakable things to Microsoft Access databases. He's also on the board of directors for a Canadian bank. Nobody knows why.
agile  programming  projectmanagement 
11 hours ago by scale
The U.S. Department of Defense on How To Detect ‘Agile BS’
Tips on finding good agile teams in large organizations:

> Are teams delivering working software to at least some subset of real users every iteration (including the first) and gathering feedback?
agile  digitaltransformation  govt 
11 hours ago by cote

« earlier    

related tags

advice  agile-scrum-fall  agile2019  agility  architecture  best  bestpractices  book  bullshit  business-agility  business  buythis  capstone  change  cheatsheet  coaching  collaboration  consultant  consulting  corporate  corporatism  culture  design  designthinking  dev  development  devops  digital  digitaltransformation  digitalworkplace  dod  dopost  dual-track  engineering  epics  ericjankaak  essentials  extreme  fail  flexibleworking  foss  fragile  free  friends  funny  gist  git  govt  guidelines  guilds  hcb  howto  humor  it  kanban  labour  leadership  lean  leanstartup  management  manifesto  manifestos  matt-lemay  meetings  methodology  metrics  microservices  military  mvp  okrs  opensource  patterns  pdf  people  planning  porsche  ppl  practices  proces  process  product-management  product  productivity  productteam  program  programming  progress  project-management  projectmanagement  projektmanagement  psychology  quality  radar  rat  recommended  reference  remote  scrum  software  softwaredev  softwaredevelopment  softwareengineering  startup  stories  team  teams  technology  things  tools  toread  user-stories  ux  vorstellungsgespräch  wekan  work 

Copy this bookmark: