Explore tweets tagged as #FocusedObjective
@VTorves
𝚟𝚝𝚘𝚛𝚟𝚎𝚜.𝚛𝚋 👨‍💻 🚀
8 years
Agile 2014 Software Moneyball (Troy Magennis) https://t.co/2i6lVVw5cw
0
0
1
@sarahtarap
Sarah Taraporewalla
6 years
Probabilistic predictability through https://t.co/kBw39B9YTG 🤯
0
1
2
@cacoEXP
Caco Mafra
6 years
Você gosta das métricas do Método Kanban, mas tem dificuldade de gerar as visualizações e os gráficos? Gostaria de uma Planilha para ajudar? O Troy Magennis resolveu isso pra vc! É GRATIS, Tks Troy! Podem baixar aqui a planilha: https://t.co/Atjzvu7Wo2 #kanban #Metrics #scrum
0
2
19
@rkasper
Richard Kasperowski
7 years
RT @t_magennis: Added Work in Progress and Aging chart to the Team Dashboard (now v3) spreadsheet. Help teams maintain constant WIP and see when the age of open work grows. Stable systems need both. Took > 3 weeks of work, so P ... https://t.co/yCVIJjzmJl
0
0
0
@t_magennis
Troy Magennis
4 years
Why Monte Carlo Forecast? & The Math of Flow Course- Newsletter from Troy Magennis - https://t.co/EJzlJnGClt
1
1
14
@t_magennis
Troy Magennis
4 years
Finding Leading Indicators - Newsletter from Troy Magennis - https://t.co/WrVcRScLhl
0
1
21
@purnimakamath
Purnima Kamath
6 years
This is so cool! Using story counts for forecasting completion dates. https://t.co/NzGRc19O4d #yownight @MichelePlayfair
0
0
0
@galleman
Glen B. Alleman, MSSM, Vietnam 69-70
8 years
@agroebbe A simple textbook example showing your conjecture is incorrect. You may want to read Troy's book https://t.co/MnaWuvnGlt where "Estimate" is used 509 times. So tell us exactly how you can model and improve flow in the presence of uncertainty without make estimates
1
0
0
@__bbak
Bruno Baketarić
5 years
@Misterme_oderso Der hat auch auf seiner Website ( https://t.co/331EPCbbI2 ) und vor allem hier: https://t.co/l1N7j9iFVD Tonnen von Informationen zum Thema.
1
0
1
@tomcudd
Tom Cudd
4 years
Here's a link to a great graph that helped explain how external dependencies delay projects.
1
0
0
@t_magennis
Troy Magennis
3 years
@Kurtis_NZ @C_Goscinski I have a free spreadsheet, someone is connecting it to JIRA, but this is the simplest tool, just start and finish dates for work needed. https://t.co/xcwgXFvO02
0
0
1
@dustinson
Dustinson
5 years
I had learned this from @mattbarcomb who originally sourced it from https://t.co/EBw50x0MPL. Change the conversation or continue to be trapped by poor constraints. "When will we be done" is a fair question to ask. How we answer it can be improved to help all.
0
0
2
@JoeButson
Joe Butson
3 years
@soph_weston @DReinertsen @Tasktop @CarlotaPrzPerez Also, in matters of Flow, Troy's offerings are quite interesting.
1
0
1
@gilligan128
Mark Henke
2 years
@Madisonkanna Automate it:
0
0
1
@ekrylov_us
Eugene Krylov
5 years
@DocOnDev https://t.co/lgU9Zmqkg4 If you are going to forecast, you need some notion of `actual`. If you are counting stories, it could be how your original story split before getting to done. For points, it could be how many Small stories on average end up Large.
0
0
1
@Kate_Catlin
Kate Catlin
6 years
A high-level on using the SAFe method or SAFe "Arnold mod" approach to better backlog prioritization https://t.co/vlVvrB2eY2
0
0
0
@0xdabbad00
Scott Piper
7 years
@libber For what did we miss, could apply Capture/Recapture estimations of separate code reviews.
1
1
5
@t_magennis
Troy Magennis
4 years
Everything went wrong :) Use this link
0
0
1
@busywait
Steven Mackenzie
7 years
There might be an interesting conversation about the age of work (and defects relative to stories) in my backlog from this data, but the chart isn't making best use of 2 axes - easier ways to plot a straight line @t_magennis :D (#Kanban Team Dashboard v3 https://t.co/AzJ9y3IO5S)
1
0
1