LKCE13

if you have six months of data, build your model based on the first three months, test it on the last three. ~ @t_magennis #lkce13

— Alexei Zheglov (@az1)2013-11-04 09:01:07

Model baseline using historical data. Check the model against the known data. Only then forecast. @t_magennis #lkce13

— Pawel Brodzinski (@pawelbrodzinski)2013-11-04 09:00:58

RT @StefanRoock: "Estimation isn't waste. We just estimate the wrong things." via @t_magennis #lkce13

— Katrin Sauer (@Ka_Sauer)2013-11-04 09:00:40

RT @az1: capture lead time, (segmented) cycle time(s), WIP day by day. Easy with any spreadsheet. ~ @t_magennis #lkce13

— Chris R. Chapman (@DerailleurAgile)2013-11-04 09:00:30

If you want more resources, people or change the process you need to justify it in €/$. Points/velocity doesn’t work. @t_magennis #lkce13

— Piotr Leszczyński (@p_leszczynski)2013-11-04 08:59:57

In making a business case for investments story points or velocity are useless. Use USD or EUR. @t_magennis #lkce13

— Pawel Brodzinski (@pawelbrodzinski)2013-11-04 08:59:45

RT @erik_schon: The importance of a shared story to break the silos ~@ourfounder #LKCE13

— Mattias Åhlander (@MatteAhlander)2013-11-04 08:59:41

RT @az1: the difference between estimate and forecast is that the forecast states its uncertainty. ~ @t_magennis #lkce13 #NoEstimates

— Chris R. Chapman (@DerailleurAgile)2013-11-04 08:59:15

RT @StefanRoock: "Estimation isn't waste. We just estimate the wrong things." via @t_magennis #lkce13

— Lean Kanban Centr.EU (@leankanbance)2013-11-04 08:59:13

Why work iteratively? Because "every time deliver something, we've eliminated its uncertainty" of not being delivered #lkce13 @t_Magennis

— Katrin Sauer (@Ka_Sauer)2013-11-04 08:58:54