I’ve come to consider that it doesn’t matter too much what activity you choose to get a discussion going. What matters most is regular reflection, hearing all the voices in a team, and making progress together. — Jono Hey in Rose, Thorn, Bud - Sketchplanations
8 Different Ways to Organize Your Backlog by Anthony Murphy, Visual Workspace for Innovation User Story Maps Backlog as a User Story Map Idea Funnel Backlog Idea Funnel Backlog feeding into a Kanban board Opportunity Backlog Splitting your backlog into two — Opportunity backlog for discovery and Development for delivery. Classes of Work Backlog Divide your backlog into multiple smaller backlogs based on different classes of work. Tree Backlog Tree backlogs are great for complex products with many different feature sets....
Backlog size is inversely proportional to how often you talk to customers As with anything, these are not absolute truths but born out of my experience. Replace planning time with talking to customers Reduce time spent on UI design; focus on technical component design instead How you think people use your app is different than how they use it Implement account spoofing Page one real estate is critical to a seamless experience Your customer is your most important marketer MVPs are pointless if you’re not going to iterate on them There is no point to having a large backlog because the bigger the backlog, the higher the unvalidated assumptions, and the lower the chance that it creates any customer value....
Michael O. Church’s answer to Why do some developers at strong companies like Google consider Agile development to be nonsense? – Quora Before I get into why this “Agile” stuff is horrible, let’s describe where Agile/Scrum can work. It can work for a time-sensitive and critical project of short duration (6 weeks max) that cross-cuts the business and has no clear manager , because it involves people from multiple departments. You can call it a “Code Red” or call it a Scrum or a “War Room” if you have a physical room for it....
The problem? For example, 3 guys wrote a paper in 86 and they said that a good estimate is an estimate that’s within 25% of the original estimate, 75% of the time … so, mostly one quarter wrong . Yikes, not a very good prospect at all. The gist of #noestimates to determine how much scope can be delivered by a given date: Select the most important piece of work you need to do (highest value first) Break that piece of work down into risk-neutral chunks of work: (…) small enough that failing to deliver it at first attempt will not jeopardize the project [typically ~1 day chunks] Develop (…) Deliver that work to a production-like environment....
#noestimates: using throughtput as a metric to predict progress Vasco Duarte ( ALE Hangout with Vasco Duarte: No Estimates @ 41:50 )
Agile Is Dead (Long Live Agility) – PragDave Back to the Basics Here is how to do something in an agile fashion. What to do: Find out where you are Take a small step towards your goal Adjust your understanding based on what you learned Repeat How to do it: When faced with two or more alternatives that deliver roughly the same value, take the path that makes future change easier....
Trello | Organize anything, together. Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what’s being worked on, who’s working on what, and where something is in a process.