Date: October 6th, 2015
Time: 2pm – 7pm, 10 minute coffee breaks every hour
Prerequisites: A laptop or tablet will be required to participate in the course.
Lecturers: Tom Gilb
Intended audience: Project managers, functional managers, IT professionals involved into decision making on budget, scope, team size on a daily basis
Participation fee: 400 UAH paid via TicketClub
Background
Most IT projects fail wholly or partly to satisfy expectations of funders and stakeholders (try Googling IT Project Failure).For those who want the ‘well hidden’ knowledge of how to succeed in IT Project Management, specific techniques will be presented in a lecture format with interaction between facilitator and the group.
Outcomes
The participants will be provided with knowledge and tools to help them
Syllabus
1 hour Briefing on Foundations
Main Project Management ‘Evo’ Subjects
About lecturer
Tom Gilb is known as the “grandfather” of Agile. He is a Senior Partner at Result Planning Limited and a frequent speaker at many conferences on requirements and project management. His references can very well sum up his impact onto Agile and project management practices.
“Tom Gilb invented Evo, arguably the first Agile process. He and his son Kai have been working with me in Norway to align what they are doing with Scrum.
Kai has some excellent case studies where he has acted as Product Owner. He has done some of the most innovative things I have seen in the Scrum community.”
Jeff Sutherland, co-inventor of Scrum, 5Feb 2010 in Scrum Alliance Email.
“Tom Gilb’s Planguage referenced and praised at #scrumgathering by Jeff Sutherland. I highly agree” Mike Cohn, Tweet, Oct 19 2009
“I’ve always considered Tom to have been the original agilist. In 1989, he wrote about short iterations (each should be no more than 2% of the total project schedule). This was long before the rest of us had it figured out.” Mike Cohn
https://www.mountaingoatsoftware.com/blog/a-requirements-challenge
Comment of Kent Beck on Tom Gilb’s book , “Principles of Software Engineering Management”: “ A strong case for evolutionary delivery – small releases, constant refactoring, intense dialog with the customer”. (Beck, page 173).
In a mail to Tom, Kent wrote: “I’m glad you and I have some alignment of ideas. I stole enough of yours that I’d be disappointed if we didn’t :-), Kent” (2003)
“But if you really want to take a step up, you should read Tom Gilb. The ideas expressed in Principles of Software Engineering Management aren’t quite fully baked into the ADD-sized nuggets that today’s developers might be used to, but make no mistake, Gilb’s thinking on requirements definition, reliability, design generation, code inspection, and project metrics are beyond most current practice.” Corey Ladas http://leansoftwareengineering.com/2007/12/20/tom-gilbs-evolutionary-delivery-a-great-improvement-over-its-successors/
voting closed