Embed Size (px)
DESCRIPTION
This class gives specific guidelines as well as case studies and references that can be used to dramatically increase the chances of success in an Agile Project.
Citation preview
TECHNOLOGY TRANSFER PRESENTS
AGILEPROJECT MANAGEMENT
EDYOURDON
ROME MAY 2-4, 2011RESIDENZA DI RIPETTA - VIA DI RIPETTA, 231
ROME (ITALY
AGILE PROJECT MANAGEMENT
ABOUT THIS SEMINAR
Though the basic principles of “Agile” software development were first published as a “manifesto” nearly adecade ago, and though some IT professionals argue they have been “Agile” for much longer than that, it hasonly been during the past year or two that it has begun to reach “mainstream” status in the IT industry. At thesame time, more IT organizations are beginning to realize that “Agile” is more than just a simple philosophy to“be flexible.”
Indeed, there are detailed, specific guidelines as well as case studies and references that can be used to dra-matically increase the chances of success in an Agile Project. Having managed, guided, coached, and lecturedabout Agile Project Management since its early days, Ed Yourdon has collected these guidelines and experi-ences into an intense, detailed seminar that will help seminar delegates succeed with their own Agile Projects.
WHO SHOULD ATTEND
Team leaders and Project Managers who intend to lead an Agile Project of their own, as well as Programmers,software Engineers, and other IT Professionals who intend to participate in an Agile Project. Also recommend-ed for mid-level and senior-level IT executives who are thinking of, or planning to, introduce an Agile “initiative”for all of the IT projects in their organization.
OUTLINE
1. Introduction
• Agenda. Objectives of the seminar
2. Why Agile is becoming main-stream
• Assumptions and problems oftraditional system developmentapproaches
• The age of complexity, uncertain-ty, and disruptive change
• The objectives of Agile: flexibility,quality, user satisfaction
• Surveys of usage and experi-ences with Agile Projects
• Summary of top 3 things neededto make Agile succeed
•When not to use an Agile approach
3. An overview of the Agileprocess
• Brief requirements and envision-ing, based on “stories”
• Developing an initial architec-ture, as needed
• Development “sprints,” with deliv-erables every week or two
• Re-planning for the next sprint• Continuous refactoring of exist-ing code/architecture
• The concept of technical debt:“always leave the code smellingbetter”
• Test-Driven Design (TDD)
4. The difference between Agileprocesses and Agile manage-ment
• Distinguishing between technicalactivities of design, coding, andtesting – versus managementactivities of planning, estimating,controlling, and supervision ofproject-team personnel
5.Key elements of Agilemanage-ment
• What Agile managers do• What they don’t do: persistingwith initial plan is biggest predic-tor of failure
• Estimating value of each deliver-able, and distinguishing between“features” and value
• Key principles: co-located devel-opers and users; Developersdedicated to one project; aban-doning traditional “command andcontrol” and encouraging more“self-management” individualsand teams
6.Managing people in Agile Pro-jects
• Recruiting technical people forAgile Projects
• Motivating and demotivatingpeople
• Basics of self-organization andself-management
• Developing competence
7.Managing teams in Agile Pro-jects
• Developing trust in teams; char-acteristics of agile teams, ene-mies of organizational trust,symptoms of mistrust
• Team roles• Empowering teams• Leading and ruling of teams; thecraft of rule-making
• Alignment of constraints. Com-munications in teams
8. Planning, estimating andscheduling Agile Projects
• The purpose of planning; whyplanning typically fails
• Estimating size of projects, withstory points, and “ideal days”
• Techniques of estimating - scrumpoker, etc.
• Re-estimating• Planning for value: prioritizingthemes; financial prioritization;prioritizing desirability
• Scheduling: release planning, it-eration planning
• Estimating velocity and burndown• Buffering plans for uncertainty
9.Monitoring and controllingprogress in Agile Projects
• The importance of frequent de-liverables
• Daily standupmeetings:what areyou going to accomplish today,what obstacles stand in your way
•Managingworkflows, not schedules• Monitoring release plans• “Retrospectives” (mini-post-mortems) to plan for next sprint
• Don’t break the build
10. Dealing with change and im-provement
• Laws of change• Embracing change• Linear vs. non-linear improvement
11. Variants and dialects of Agile
• Scrum• Lean development• XP (extreme programming)• Other variants
12. Confronting the myths ofAgile
• Agile doesn’t scale, and can’t beused on large projects
• Agile cannot be used on geo-graphically distributed projects,where developers and users arenot co-located
• Agile cannot be used on projectswith external “regulatory” require-ments
• Agile means there will be no doc-umentation
• Agile is mortally opposed to formalapproaches such as SEI/CMMI,Esprit, ISO-9000, etc.
13. Tools for Agile
• Collaboration and communica-tion tools
• Project Management tools fortracking and displaying progress,status, etc
• Additional tools
14. Conclusion
ED YOURDONAGILE PROJECT MANAGEMENT
May 2-4, 2011Residenza di RipettaVia di Ripetta, 231Rome (Italy)
Registration fee:€ 1600
If registered participants are unable to attend,or in case of cancellation of the seminar, thegeneral conditions mentioned before areapplicable.
first name ...............................................................
surname .................................................................
job title ...................................................................
organisation ...........................................................
address ..................................................................
postcode ................................................................
city .........................................................................
country ...................................................................
telephone ...............................................................
fax ..........................................................................
e-mail .....................................................................
�
Send your registration formwith the receipt of the payment to:Technology Transfer S.r.l.Piazza Cavour, 3 - 00193 Rome (Italy)Tel. +39-06-6832227 - Fax +39-06-6871102info@technologytransfer.itwww.technologytransfer.it
Stamp and signature
INFORMATION
PARTICIPATION FEE
€ 1600
The fee includes all seminardocumentation, luncheon and coffeebreaks.
VENUE
Residenza di RipettaVia di Ripetta, 231Rome (Italy)
SEMINAR TIMETABLE
9.30 am - 1.00 pm2.00 pm - 5.00 pm
HOW TO REGISTER
You must send the registration form withthe receipt of the payment to:TECHNOLOGY TRANSFER S.r.l.Piazza Cavour, 3 - 00193 Rome (Italy)Fax +39-06-6871102
withinApril 18, 2011
PAYMENT
Wire transfer to:Technology Transfer S.r.l.Banca Intesa Sanpaolo S.p.A.Agenzia 6787 di RomaIban Code:IT 34 Y 03069 05039 048890270110
GENERAL CONDITIONS
GROUP DISCOUNT
If a company registers 5 participants tothe same seminar, it will pay only for 4.Those who benefit of this discount are notentitled to other discounts for the sameseminar.
EARLY REGISTRATION
The participants who will register 30 daysbefore the seminar are entitled to a 5%discount.
CANCELLATION POLICY
A full refund is given for any cancellationreceived more than 15 days before theseminar starts. Cancellations less than15 days prior the event are liable for 50%of the fee. Cancellations less than oneweek prior to the event date will be liablefor the full fee.
CANCELLATION LIABILITY
In the case of cancellation of an event forany reason, Technology Transfer’sliability is limited to the return of theregistration fee only.
Ed Yourdon a veteran of the IT industry for nearly 45 years, Ed Yourdon has been deeply involved in the Internetrevolution since it began in the mid-1990s; he has served on Boards of Directors and technical advisory boardsfor numerous high-tech startup companies in the U.S. and India. He has been involved in Enterprise 2.0 since itsbeginnings in the 2002-2003 period, and he currently consults, lectures, and writes about various aspects of thenew technologies. Mr. Yourdon will summarize the technologies, identify the strategic issues facing IT managersand senior executives today. He is an internationally-recognized computer consultant, as well as the author ofmore than two dozen books, including: “Byte Wars”, “Managing High-Intensity Internet Projects”, “DeathMarch”, ”Rise and Resurrection of the American Programmer”, and “Decline and Fall of the American Pro-grammer”. His latest book, “Outsource: competing in the global productivity race”, discusses both currentand future trends in offshore outsourcing, and provides practical strategies for individuals, small Businesses, andthe nation to cope with this unstoppable tidal wave. According to the December 1999 issue of “Crosstalk: TheJournal of Defense Software Engineering”, Ed Yourdon is one of the ten most influential men and women in thesoftware field. In June 1997, he was inducted into the Computer Hall of Fame, along with such notables asCharles Babbage, Seymour Cray, James Martin, Grace Hopper, Gerald Weinberg, and Bill Gates.
SPEAKER
