130 likes | 258 Views
The XP experience in Fst. Workshop SANE 4-10-2002 Orlando Murru. Fst original motivations. Experiment with SW development methods that promised improvements over RUP, especially in relation to: Size of the project documentation. Code quality. Professional growth of junior staff.
E N D
The XP experience in Fst Workshop SANE 4-10-2002 Orlando Murru
Fst original motivations • Experiment with SW development methods that promised improvements over RUP, especially in relation to: • Size of the project documentation. • Code quality. • Professional growth of junior staff. The XP experience in Fst
Our experience with XP • 24 month of eXPerience • Up to 15 people involved • 3 projects completed, 4 projects in progress • Limited external coaching/tutoring The XP experience in Fst
XP introduction in Fst • E-Sign R&D projects: e-business portal using strong signatures, time-stamping etc. • First project: digital signatures components and technologies. XP without planning game (April-June 2001). • Second project: integration of technologies in portal: Full XP (July-October 2001) The XP experience in Fst
XP introduction in Fst (cont.) • CONSIP: January-July 2002, 7 people. Full XP, limited coaching. • Other small projects (2, 3 people) • Present day: 15 people using XP in three distinct e-governments product development projects: e-auctions, certified mail, PKI components. The XP experience in Fst
XP practices current usage ranking The XP experience in Fst
Two different, incompatible models The XP experience in Fst
XP benefits • XP practices give immediate, visible returns to the individual programmer: better quality, enhanced awareness, more participation. • XP makes it easy to add junior members to a team. • XP provides a better model to integrate and put to work experience and seniority, and to keep senior staff’s competences up-to-date • XP provides a very good feed-back on the state of the project The XP experience in Fst
Problems • Management supervision is less effective on a XP team. • Doubts and resistance against XP increased when we moved from • Experienced programmers. • QA people • Inexperienced programmers. • Project managers and team leaders. • Customers and business people. The XP experience in Fst
Problems (cont.) • Requirement prioritization is in contrast with fixed scope contracts. • Not enough exploratory phase. • Programmers’ experience is as important in XP as in any other methodology The XP experience in Fst
XP impacts • XP has been invisible to the external customer • We are not able to assess quantitatively if it was a success in terms of cost. • Success in terms of staff satisfaction, flexibility of the process, validity and timeliness of the deliverables, quality (?) The XP experience in Fst
XP Roadmap • We are looking forward to the next XP projects. We want to achieve: • Better exploration • Better coaching • Better system level testing • Better architecture • Integration in the quality system. The XP experience in Fst
Does XP have a future? • As long as it is considered more of a philosophy than a defined process. The XP experience in Fst