A take on injecting reality into software planning at any stage

  1. Justifies using an overall timeline for software development by providing responsibilities that flow both up and down the organization and makes this information actionable.
  2. Balances the stakes of creating estimates up and down the organization, causing someone pushing to make the timeline shorter to take on greater risk, which is now not normally true.

How to impose responsibility on parties to a project plan without just making everything into an interminable crunch that winds up destroying everything

This is a healthy way to start a project regardless of the relationship between players




An old programmer learning new tricks.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Delay in the old API deprecation, and Linux client launch

Differences between Static and Dynamic (shared) Libraries

Onboarding and performance

The Art of Using Open Source to Open New Data Doors with the Co-Founders of OpenMetadata

Append/Concat/Join/Merge/ — Demystified

Sign your AWS Lambda packages

Squirrel Weekly (19/01) 🐿️

PHPArkitect: Put your architectural rules under test!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
art yerkes

art yerkes

An old programmer learning new tricks.

More from Medium

How to get results effectively in your engineering side job with Agile practices

Meeting Mayhem! #WFH

Benefits of The Agile Development Methodology —Post by Meeraki Software Solutions

Kanban at all levels for your organization