(work in progress)

Split into small batches. Really small user stories. Each deliverable and shippable.

It makes everyone happy. Product owners and stakeholders and developers (there's nothing more motivating than someting that works). Constantly added value.

And if things go wrong, it's easier to sacrifice and live with waste of 3 days of work of 1-2 guys rather than 1 month of whole development team.

Kaizen philosophy -> continous improvement in small steps.

GitHub: -> separate post -> work as an open source project

• work async (nobody pulling out of the zone)
• no meetings, no deadlines, no managers, no work hours
• time flexibility - work whenever and wherever you want
• log all the things - everyone on the same page
• chatrooms - no presence needed
• work on what you want
• work where i want
• work when i want
• work like open source project
• pull requests for code review and any new code, for discussions (code, feature, strategy), for everything related feature
  • simple branching (master -> branch)
  • everyone can push, everyone can deploy
  • master is always deployable
    • you can deploy to staging or to production box
  • getting shit done without wasting a lot of time
• issues
  • keep it simple, without any meta-information
  • todo list (tasks) within issue as a list (of checkboxes)

http://zachholman.com/posts/how-github-works/ http://zachholman.com/talk/how-github-uses-github-to-build-github/