ThanksThanks.
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at https://groups.google.com/group/scrumalliance.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at https://groups.google.com/group/scrumalliance.
For more options, visit https://groups.google.com/d/optout.
On Feb 3, 2016, at 11:03 AM, Jeff Sieffert <je...@spiekerpoint.com> wrote:The size of the project really has no bearing when talking Agile. Every single task is broken down into small manageable pieces that can be easily estimated and completed. The larger the project you have just equates to more tasks. The most difficult thing to manage will then become keeping all of those tasks prioritized effectively.
Gustavo the article of dated. The state of the art has moved a long way in that time. Look at less.works for some ideas.
Hint from personal experience many ERP implantations fail because there is a large gap between the capability of the tools, the goals of the customer and the quality of the data. Agile would force people to confront the disconnect early.
Cheers
Mark
Mark Levison | 1 (877) 248-8277 | Twitter | LinkedIn | Facebook Certified ScrumMaster Training: Vancouver | Edmonton | Ottawa | Montreal | Toronto Certified Product Owner & Private Training also available ~ Our Training Schedule Agile Pain Relief Consulting | Notes from a Tool User Proud Sponsor of Agile Tour Gatineau Ottawa and Agile Coach Camp Canada |