Episode #30

Nuts and Bolts


Despite 99 reasons to NOT get stuff done, the guys show off their latest accomplishments, as well as those in the community, and how scrum purports to provide a framework for all of it.

Intro

News / Community Updates

OurCompose Developments

Integration Discussion - Bitwarden - Initial Configuration

Grab Bag - Scrum

Feedback Loops, The Government’s $110M Mistake

Government contracts, 1000 page papers no one reads, and a plan

Everything looks better on paper.. But what happens when the plan goes awry?

FBI had a plan to modernize information sharing. After three years and millions of dollars later they didn’t bother looking at the process, but rather signed another contract with a contractor. Of course as defects arose, and when they were far behind they decided to look at a new approach to the project.

Scrum reduces the feedback cycle, and forces a continuous inspection and adaption cycle forcing the question “why” at every task verifying the need and/or how it can be improved.

Basically Asking:

Lessons great companies have

“A team has to demand greatness from itself.”

One Task at a time

Something that is half done isn’t done. It’s essentially all or nothing when it comes to tasks. You can’t have something that exists as 50% complete as complete.

Do one thing exclusively before moving on to another project.

Do It Right the First Time. When you make a mistake, fix it right away. Stop everything else and address it. Fixing it later can take you more than twenty times longer than if you fix it now.

Only Plan What You Need To. Don’t try to project everything out years in advance. Just plan enough to keep your team busy.

It has been proven humans are terrible at planning in hours.

Communication

Everyone knows Everything. Communication saturation accelerates work.

One Meeting a Day. When it comes to team check-ins, once a day is enough. Get together for fifteen minutes at the Daily Stand-up, see what can be done to increase speed, and do it.

Roles

Development Team: every team has members with the necessary skills to design, build, and test the product, and everyone participates in the development process from the beginning to the end. Teams are multifunctional.

Scrum Master: Someone familiar with the Scrum structure, acting as an advisor and as a facilitator, with the goal to help the team identify and deal with impedements that arise through the project.

Product Owner: in contact with the stakeholders, receiving opinions, and feedback from customers. Role exists to relay vision and decisions from customer point of view

Priorities

The key is what you decide to do first:

Aim for REVENUE first, figure out the 20% of input that yields 80% of the output.

What is something that takes 20% to ship to the customer we can build the other 80% later?

Thinking most value for the least effort


The tools we use to get it done

At Compositional Enterprises, we value our time as much as you do. That's why we only use the best Free, Libre, and Open Source tools to produce our quality content and products.

Take action and start using the same secure and convenient tools that we use by signing up for your OurCompose instance today! Invest in your community by donating directly to the podcast! Every bit (and byte) goes back into growing and spreading the show. Otherwise, to stay updated with the show and all future developments, find us on reddit or sign up for our mailing list using the form below!