www.archive-org-2013.com » ORG » X » XP2011

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 158 . Archive date: 2013-12.

  • Title: XP 2011
    Descriptive info: .. Home.. News.. Program.. Organization.. Venue.. Photo Gallery.. Videos.. The 12th International Conference on Agile Software Development, XP2011, is a leading international conference on agile methods in software and information systems development.. XP2011 will be hosted by Universidad Politécnica de Madrid (Technical University of Madrid, UPM), in Spain.. The conference brings together both industrial practitioners and researchers in the fields of information systems and software development, and examines latest theory, practical applications, and implications of agile methods.. XP2011 encourages submissions of high quality research papers, workshops, experience reports, posters, tutorials, PhD symposium papers, and lightning talks, an opportunity to share important ideas or experiences in ten minute slots.. The topics of interest in the conference include, but are not restricted to, the following:.. Adoption and diffusion of agile methods.. Implementing agility in global software development.. Agile Offshore and Agile Software Factories.. Empirical studies and experiences of agile methods.. Tools and techniques for agile development.. Social and human aspects of agile methods.. Organizational agility.. SOA based systems and agile development.. Measurement and metrics for agile projects and enterprise.. XP evolution, new XP trends or XP proposals of update.. Agile for IT Development.. Agility in systems engineering and safety critical systems.. Software and systems architecture in an agile environment.. Legacy systems and agility.. Agile usability.. Management and governance aspects of agile methods.. Implications of agile methods for industrial practice.. Foundations and conceptual studies of agile methods.. Implications of agile methods for research and education.. Collaborators:.. Official Airline:.. Changes in the program.. Kati Vilkki's talk has been moved from Thursday 12th at 17:00 to Wednesday 11th at 11 (after the keynote).. Read more.. 11.. 05.. 2011.. Conference Dinner.. Wednesday 11th May 2011.. 09.. Last minute information.. File with useful information of XP2011.. How to reach the venue from the airport.. Information about public transportation.. List of events.. 02.. Program printed version available.. It is available the printed version of the final XP2011 program.. Read our news archive.. Highlights from the program:.. Agile Testing Journey - From Specification to Done.. Effective testing should be an integrated part of agile development.. Various agile testing practices, such as ATDD, TDD, and exploratory testing, have been introduced.. In practice it's not clear how to combine these effectively.. Agile testing requires various skills and has to be done in parallel with development.. Right balance between information, cost and feedback time is needed to achieve this.. In this workshop we explore the testing activities required to get the feature done.. [.. Read more.. ].. Agile Management: Leadership on an Agile environment.. For a long time, Agile literature have been focused on development practices, teamwork, processes and tools.. On an Agile environment, the manager's role changes from the Command & Control system to a Servant Leadership & Role Model paradigm whose main responsibilities include impediments removal, constraints and goals definition, and, most important of all, corporate culture definition and improvement.. The Agile Manager also has a leading role on change management and should act as a sponsor and a catalyst on an Agile Implementation project.. Wednesday's Keynote.. Keynote speaker:.. Esther Derby.. This year marks 10 years since the signing of the Agile Manifesto.. In those 10 years, we've seen notable successes.. We've also seen XP-B, Scrum-but, Fragile, and just plain #FAIL.. Organizations have adopted agile methods to solve all manner of problems.. But no method can solve problems unless management also changes.. And that's a matter of changing minds, mindsets, and what matters to managers.. A Simple Approach to Modular Design.. When I tried to learn object-oriented design, I read the classics.. At least I tried to read the classics.. It didn't go that well.. It wasn't until I began practising test-driven development that I began to truly understand the principles of object-oriented design, including how to use them effectively to drive down the cost of adding features.. Silo Busting.. In this tutorial, we explore the causes of organizational silos, their impacts, and the strategies that you can employ to help mitigate their impact on your teams and within your organization.. Contact details: Tom Perry: tperry@cybersource.. com and Lourdes Vidueira: lvidueira@cybersource.. com [.. Retrospectives in action.. A This tutorial offers something for everyone to learn how to use retrospectives to foster a culture of continuous improvement.. People new to agile methods will learn what retrospectives are, why they are so important and some of the key elements to how to make them successful.. Agile testing and critical systems.. It is a widely shared impression that the agile community and the critical system community live in completely different worlds.. Actually, the critical  ...   about why we measure and the fallacy of the "measure everything" mindset.. Then we'll discuss the popular metrics used today and the pitfalls of using them.. We will explain the powerful concept of challenging existing norms and empowering team members to define their own standard work.. Finally, we'll close with a discussion on how to avoid the lean/agile treadmill by keeping things new and exciting.. http://dhondtsayitsagile.. blogspot.. com.. Extreme Startup.. In this workshop we aim to simulate product teams building software and delivering it into a market.. You can continue to refine and upgrade your software throughout the session, releasing new versions and testing their performance in the market.. Once your software is live it will begin to accrue points, as simulated users use the software and score it against how well it fits their needs.. Acceptance Test Driven Development (ATDD) with Robot Framework.. Executable requirements neatly combine two important XP practices: user stories and acceptance testing.. They enhance communication, ease following the number of running tested features during an iteration, and work as regression tests in future iterations.. This workshop gives an introduction to this important process and also shows how it is used in developing a realistic system.. Participants can also join the fun and get real hands-on experience.. Learnings from this tutorial are thus applicable when using other acceptance testing tools such as Cucumber, FitNesse, TextTest, or Concordion.. On this half-day tutorial (240 mins), attendees will learn: What Agile means to a Corporate Culture and the old-style management, What to expect from a self-organized Agile Team and how Command & Control kills Agile, How to manage complex systems ? or not, The Managers role on motivation, development and alignment, The Managers role on at the portfolio level: planning, measuring and executing on an Agile Environment.. The Fit of Software Development in the Larger Organization.. This tutorial will address three critical issues in software development today: 1.. Building the Right Thing ' How does the software development organization fit into the overall company and provide the capabilities that are most critical to the company's success' 2.. Leadership A Product Manager is an outward facing role, while a Product Owner is an inward-facing role; can one person manage both roles? 3.. Design Thinking Dealing with complexity is the essence of software development; how does design thinking help manage complex environments? [.. Agile Software Development with Distributed Teams.. On the one hand there are meanwhile not many projects left that are made at home without outsourcing, off- or nearshoring.. Thus, global software development seems to be a fact in state-of-the-art software development.. On the other hand more and more projects discover the success factor of agile software development not only since the Standish Group is recommending this approach.. However, there are still a lot of people who believe agile software development is for small and collocated teams only.. Teaching and Learning TDD in the Coding Dojo.. Emily Bache will facilitate a tutorial where you will experience Test Driven Development in the safe environment of a Coding Dojo.. Take the chance to improve your skills and practice agile coding techniques with other programmers.. We'll spend the last part of the session discussing experiences using the Coding Dojo to teach TDD and agile programming in general.. Brutal Refactoring.. There is a lot of tacit knowledge in the industry about refactoring, but there are also some very hard cases.. Some code is so inscrutable that it defies most attempts to make it understandable.. Developers are tempted to throw it away and start over again, but as always, they are stymied by the fact that they don?t really understand what they want to replace.. In this tutorial, Michael Feathers will present a number of aggressive refactorings that can be used to move nearly intractable code up to the next level of maintainability.. Refactoring in the 4th Dimension.. Physicists tell us that there are at least four dimensions that are important to us.. We typically only think of the three spatial dimensions: length, width, and depth, but time is a dimension as well.. In this workshop, we will mine the change histories of several open source projects and use them to identify patterns that unfold in time within codebases.. Participants in this workshop should bring a laptop with Java development tools installed and Ruby 1.. 8.. Join our group at LinkedIn.. anttiki.. :.. Your change to be the CTO or Head of Finance Products! Portfolio Planning Game starting 13:30 @ A.. Schönberg.. #xp2011.. 13:08 PM Jun 06.. from.. Twitter for iPhone.. Gold sponsors:.. Silver sponsors:.. Bronze sponsors:..

    Original link path: /
    Open archive

  • Title: News
    Descriptive info: ">.. Show previous news articles.. Choose a year.. 2013.. 2012.. 2011.. 2010.. 2009.. Choose a month.. January.. February.. March.. April.. May.. June.. July.. August.. September.. October.. November.. December.. Date.. Title.. 2011.. 04.. Microsoft is new Silver Sponsor.. 29.. 03.. Keynote by Esther Derby.. 23.. Paradigma is new Gold Sponsor.. 12.. Autentia is new bronze sponsor.. Hotel Venue Information.. 25.. 02.. Program updated.. 22.. Eventbis is supporting XP2011.. Preseria is supporting XP2011.. Kantega is supporting XP2011.. 01.. Hotel accommodation.. Submission system closed.. Submission calls published.. Program committee published.. Organizing chairs published.. 27.. 10.. 2010.. Website for XP2011 launched..

    Original link path: /news/
    Open archive

  • Title: Program
    Descriptive info: Show all session info.. Printable version of the complete program.. (.. download.. ).. Tuesday May 10.. th.. 09:00-16:00.. PhD Symposium.. PhD Symposium.. Tuesday, 10 May 2011: Workshop / Tutorial Day.. 09:00-13:00.. Teaching and Learning TDD in the Coding Dojo (Tutorial) by Emily Bache.. Teaching and Learning TDD in the Coding Dojo (Tutorial) by Emily Bache.. Emily Bache.. (Tutorial, 4 hours) [.. Link.. ].. Take the chance to improve.. your skills and practice agile coding techniques with other programmers.. We’ll spend the last part of the session discussing experiences using the Coding Dojo to teach TDD and agile programming in general.. If you are already competent with TDD, you can use this tutorial as a way to learn the Coding Dojo method of teaching, and perhaps hold similar meetings at your workplace or local agile user group.. http://bacheconsulting.. com/.. Making feedback work in your teams (Workshop) by Mark Needham.. Making feedback work in your teams (Workshop) by Mark Needham.. Mark Needham.. (Workshop, 4 hours) [.. Feedback in peer groups allows us to rapidly move from forming, storming and norming stages, to performing.. On Agile teams that are focussed on communication, this is key to success.. In this workshop, I will share with you how we approach feedback at my workplace and explain some of the principles we use to give and receive feedback every day.. Agile testing and critical systems (Workshop) by Jorgen Boegh, Juan Garbajosa and Axel Rennoch.. Agile testing and critical systems (Workshop) by Jorgen Boegh, Juan Garbajosa and Axel Rennoch.. Jorgen Boegh, Juan Garbajosa and Axel Rennoch.. However, we think there are mutual benefits of bringing the two communities together.. For example, agile testing approaches can most likely bring many advantages to critical system testing.. These possibilities are currently not well understood and exploited.. Agile Software Development with Distributed Teams (Tutorial) by Jutta Eckstein.. Agile Software Development with Distributed Teams (Tutorial) by Jutta Eckstein.. Jutta Eckstein.. However, the agile value system and the principles as stated in the manifesto don’t argue about project size and distribution.. Yet, agile software development requests –among other things– an emphasis on face-to-face communication, which seems to contradict with globally distributed environments.. In this session, Jutta will report from her experiences in bringing the two trends –agile and global– together and on which practices help and which hinder the success of such a project.. The following questions are the focal point of the tutorial: What are the possibilities to overcome the challenges global software development provides, and what are the success factors for implementing an agile software development process within such constraints? Jutta’s own experiences are mainly based on large global agile projects in embedded and commercial software development.. A Simple Approach to Modular Design (Tutorial) by J.. B.. Rainsberger.. Rainsberger.. J.. It didn’t go that well.. It wasn’t until I began practising test-driven development that I began to truly understand the principles of object-oriented design, including how to use them effectively to drive down the cost of adding features.. After a while, I recognised that I had really learned the principles of modular design in general, and not just of object-oriented design in particular.. Since I learned those principles this way, I also teach them this way.. This is not a class in test-driven development, although we will review the fundamentals of test-driven development.. Instead, in this class we focus on how to use a small number of simple rules to generate truly flexible designs: that is, designs that actually flex as you add more features.. jbrains.. ca.. http://blog.. thecodewhisperer.. com.. twitter.. com/jbrains.. Self-Organizing Agile Teams: Beyond the Buzzword (Tutorial) by Rashina Hoda and Esther Derby.. Self-Organizing Agile Teams: Beyond the Buzzword (Tutorial) by Rashina Hoda and Esther Derby.. Rashina Hoda and Esther Derby.. Based on an original, industry-based PhD research and practical experience of mentoring numerous Agile teams, this tutorial provides an overview of self-organizing teams from multiple perspectives; a detailed description of what it means for Agile teams to be self-organizing; and practical tips to help software practitioners better understand their roles and responsibilities in establishing and sustaining self-organizing Agile teams.. 13:00-15:30.. Lunch.. Lunch.. 15:30-18:30.. Agile Testing Journey - From Specification to Done (Workshop) by Tiina Kiuru and Markus Hjort.. Agile Testing Journey - From Specification to Done (Workshop) by Tiina Kiuru and Markus Hjort.. Tiina Kiuru and Markus Hjort.. (Workshop, 3 hours) [.. We try in practice defining specifications by example, test automation and exploratory testing.. We also look into how to improve based on the information gotten from testing.. How to Sabotage the Lego City Scrum Game (Workshop) by Olaf Lewitz and Marc Löffler.. How to Sabotage the Lego City Scrum Game (Workshop) by Olaf Lewitz and Marc Löffler.. Olaf Lewitz and Marc Löffler.. Ever met a dysfunctional team mate? Then you know what we’re talking about.. Most of them didn’t mean to, they just behaved in a way that was dysfunctional in the team context.. But what you tend to initially see is only the surface and not the real reason.. Once you start to dig deeper to find the real causes you’ll find out that everything can be tracked back to four root causes.. We call them “The four evil root causes from hell”: Ignorance, Fear, Indolence, Apathy.. In our session we will play the Lego City Scrum Game.. But instead of a full team of motivated people there will be some team mates behaving strange, trying to jeopardize our project goal.. Join us to find out how to cope with such team mates to build better teams.. Second XP Workshop about Dealing with usability in an agile domain (Workshop) by Ana Maria Moreno and Agustin Yagüe.. Second XP Workshop about Dealing with usability in an agile domain (Workshop) by Ana Maria Moreno and Agustin Yagüe.. Second XP Workshop about Dealing with usability in an agile domain.. Ana Maria Moreno and Agustin Yagüe.. During XP 2010 a first edition of this workshop was held with about 25 attendees, who actively participated in an interesting debate about the topic and highlighted many open issues.. To present in the workshop, contributors would be required to submit a position paper or an experience report and receive advance approval of the organizing committee (to ensure relevance and quality of contributions).. Those submissions should not exceed 4 pages in length in Springer's LNBIP format.. http://wdua2011.. eui.. upm.. es/.. Getting Started & Leading a Kanban Initiative (Tutorial) by David Anderson.. Getting Started & Leading a Kanban Initiative (Tutorial) by David Anderson.. Getting Started & Leading a Kanban Initiative.. David Anderson.. (Tutorial, 3 hours) [.. Many people have now heard of Kanban.. Plenty of XP 2011 attendees will be familiar with boards to visualize work and work-in-progress limits and the concept of "pull.. " However, how do you go about leading a Kanban initiative in your organization? Where do you start? What goals should you set? How do you avoid resistance to change? This 180 minute tutorial will cover material that is either unpublished or available only in chapter 15 of the book Kanban - Successful Evolutionary Change for your Technology Organization.. This material is normally part of the 3-day advanced workshop on Kanban Leadership & Coaching.. There will be an assumption that attendees have a foundational level understanding of Kanban, its principles and practices.. What they are seeking is advice on leading a Kanban initiative to success.. In the first half, the tutorial will cover the principles (briefly), and then move on to discuss evolutionary change and reasons for resistance.. It will look at emotional versus logical intelligence and emotional reasons for change.. Avoiding emotional resistance through intentional choices of how to implement a kanban system design and introduce Kanban will be discussed.. When emotional resistance does occur attendees will learn how to predict its occurrence and how to overcome it with a stronger emotion.. The group will reflect on strong positive and negative emotions for motivation and how they affect an outcome.. In the second half, the tutorial will cover the material from chapter 15 of the Kanban book.. This looks at the specific mechanics of getting started with an initiative.. At setting goals and building a consensus agreement around them.. It will lay out 12 steps to go through to get started including shuttle diplomacy and how to negotiate the kanban system design, including classes of service and capacity allocation in order to get multiple competing stakeholders on-board with the implementation.. Attendees will leave motivated to get started and with new insights on how to be successful.. This material is normally covered on the first morning of a 3-day workshop.. Over 100 people attended these workshops in 2010 paying $3000 each.. Often feedback at lunch on the first day was these insights were worth the entire price of attending.. For some others, further down the line with Kanban, it has given them insights into why they've struggled or what they might have done differently.. Brutal Refactoring (Tutorial) by Michael Feathers.. Brutal Refactoring (Tutorial) by Michael Feathers.. Michael Feathers.. Developers are tempted to throw it away and start over again, but as always, they are stymied by the fact that they don’t really understand what they want to replace.. The goal isn’t to make the code clean or pretty, but simply manageable.. The techniques will focus on invasive changes that can be made on code with highly conditional logic and massive temporary variable usage.. Agile Management: Leadership on an Agile environment (Tutorial) by Angel Medinilla.. Agile Management: Leadership on an Agile environment (Tutorial) by Angel Medinilla.. Angel Medinilla.. Front-line roles like those of the Scrum Master / Agile Coach or Product Owner have been described, and some organizational guidelines have been described under the “Enterprise Scrum” or “Scaling Agility” tags.. But it is only recently that the manager’s role on an Agile Environment is being deeply discussed and described.. Depicted as “chickens” for more than a decade or even characterized as “the bad guy” by the most radical Agilists, their importance on the successful development of an Agile Corporate Culture and an Agile Environment where teams can strive and improve is scarcely studied.. The traditional Command & Control management style must be dropped, says Agile.. Teams must self-organize.. Management must step aside.. This kind of message is wholeheartedly embraced by Agile teams that have suffered bad management for decades, but managers are less likely to embrace a concept that, sometimes, seems to pursue the banishment of all management from earths surface.. On an Agile environment, the manager’s role changes from the Command & Control system to a Servant Leadership & Role Model paradigm whose main responsibilities include impediments removal, constraints and goals definition, efforts alignment, growth management, team and individual development and, most important of all, corporate culture definition and improvement.. On this half-day tutorial (240 mins), attendees will learn: What Agile means to a Corporate Culture and the old-style management, What to expect from a self-organized Agile Team and how Command & Control kills Agile, How to manage complex systems – or not, The Managers role on motivation, development and alignment, The Managers role on at the portfolio level: planning, measuring and executing on an Agile Environment.. The intended audience include: Middle and top managers on an Agile environment or willing to launch an Agile adoption program on their organization, Project Managers on an Agile transition, Team Leaders that want to mentor their managers on the Agile Way, Agile coaches, Agile evangelists, Change Managers, Anyone interested on the Agile Corporate Culture concept, Anyone involved on an Agile transition / adoption project.. Wednesday,11 May 2011: Main Conference.. 09:00-10:30.. Keynote by Esther Derby:.. Still No Silver Bullets.. Esther Derby.. (Keynote, 90 min) [.. 10:30-11:00.. Coffee break.. Coffee break.. 11:00-12:00.. Methods.. Methods.. Simulating Kanban and Scrum vs Waterfall with System Dynamics.. Luisanna Cocco, Katiuscia Mannaro, Giulio Concas and Michele L.. Marchesi.. (Research, 30 min) [.. Nowadays, Scrum is the most used Agile Methodology, while the Lean-Kanban approach is perhaps the fastest growing AM.. On the other hand, traditional, waterfall-like approaches are still very used in real-life software projects, due to the ease of up-front planning and budgeting, that however are seldom matched upon project completion.. In our opinion, more effort is needed to study and model the inner structure and behavior of these approaches, highlighting positive and negative feedback loops that are strategic to understand their features, and to decide on their adoption.. In this paper we analyze the dynamic behavior of the adoption of Kanban and Scrum, versus a traditional software development process such as the Waterfall approach.. We use a system dynamics model, based on the relationships between system variables, to assess the relative benefits of the studied approaches.. The model is simulated using a commercial tool.. The proposed model visualizes the relationships among these software development processes, and can be used to study their relative advantages and disadvantages.. Using Function Points in Agile Projects.. Célio Santana, Fabiana Leoneo, Alexandre Vasconcelos, Cristine Gusmão.. Agile Project became real in an organizational software development environment, this paper, examines whether function points would be useful to estimate how long it would take to implement a story or to complete a release estimate how long it would take to implement a story or to complete a release on Scrum projects.. Specifically, it addresses the question of whether function points would be a good measure of velocity.. Though any unit of measure can be used, this paper contrasts theoretical concepts about Story Points (SP) and function points (FP) as units for measuring size.. Also, was realized a statistical correlation between SPs and SPs using 2191 stories and 18 iterations in a Brazilian public agency.. The conclusion drawn from this study is that function points, in that particular case, could be related with the initial value of the Story Points found after the planning poker.. TDD.. TDD.. A Test-Driven Approach for Extracting Libraries of Reusable Components from Existing Applications.. Elaf Selim, Yaser Ghanam, Chris Burns, Teddy Seyed and Frank Maurer.. In agile approaches such as Extreme Programming, time is not spent on making sure that system components can be reused in similar systems.. Therefore, there is a need to investigate whether reuse can be achieved by extracting reusable assets from existing applications.. This paper presents an approach that relies on refactoring and testing practices for extracting reusable assets from existing applications.. The approach creates reusable APIs in a bottom-up fashion, on demand when a new application might benefit from component in an existing application.. The extraction process is guided and supported by the usage examples and the testing scenarios in the existing application and the new one.. The paper presents a case study, where the approach was used to extract components from the user interface of an existing application, wrap these components in an API, and use this API in the existing and new applications.. Test-Driven Development of Graphical User Interfaces: A Pilot Evaluation.. Theodore D.. Hellmann, Ali Hosseini-Khayat and Frank Maurer.. (Research, 20 min) [.. This paper presents a technique for test-driven development of GUI-based applications, as well as a pilot evaluation.. In our approach, user interface prototypes are created in such a way as to allow capture/replay tools to record interactions with them.. These recordings can then be replayed on the actual GUI as it is being developed in a test-driven fashion.. The pilot evaluation found that developers integrated GUI tests, based on user interface prototypes, into their development process and used them as a way to determine when a feature is actually complete.. Study participants felt that TDD of GUI based applications is useful.. Discussion by Esther Derby: No Silver Bullets.. Now What?.. Now What?.. No Silver Bullets.. (Discussion, 60 min) [.. Following her talk at XP2011, Esther will hold a facilitated discussion.. In this session, we'll explore why silver bullets are so appealing, and how we can counter that appeal.. We'll share stories, strategies, and tactics that really work to improve our ability to deliver valuable software.. Invited Talk by Kati Vilkki: When agile is not enough.. When agile is not enough.. Kati Vilkki.. (Invited Talk, 1 hour) [.. Recently I have been asked often "we have tried this agile thing now for 1-2 years.. What should we do next to improve?".. People feel that agile does not bring the desired business benefits and something else is needed.. Very often what is being done in practice is not very agile, though.. In order for real change to happen we need to start thinking differently about many things and that is hard.. Agile provides a good framework ´for improving SW development, but it is not enough when SW is only part of the product, in very large-scale development (tens of teams, systems of systems development) or when there is need to improve the way the whole organization works.. Agile does not give enough framework for business management and other functions outside of R&D, something more is needed.. For this "more" I recommend combining lean thinking and beyond budgeting to agile.. Lean and agile complement each other in many areas, but there are also challenges in combining these two.. Agile is very much team oriented and bottom-up approach works well in agile adaptation.. Lean requires more top-down approach and involvement of larger organizations - or course it can be used also on team level.. Another interesting difference is the role managers, which agile and lean see very differently.. In this case it could be said that lean addresses the role of management which agile mostly omits.. Agile and lean are not enough either, many of the traditional financial, planning and HR practices should also be changed to enable empowerment and lean way of working.. For these issues we are now experimenting with bringing in some thoughts from beyond budgeting.. So agile is not enough, we need a change in the whole management philosophy.. Sponsor Bazaar.. Sponsor Bazaar.. Kantega.. (Sponsor Bazaar, 1 hour) [.. 12:05-13:05.. PyUseCase : a new approach to agile GUI testing (Demo) by Emily Bache / Acceptance Testing with Robot Framework (Demo) by Janne Härkönen and Pekka Klärck.. PyUseCase : a new approach to agile GUI testing (Demo) by Emily Bache / Acceptance Testing with Robot Framework (Demo) by Janne Härkönen and Pekka Klärck.. PyUseCase : a new approach to agile GUI testing.. Geoffrey Bache.. (Demo, 30 min) [.. PyUseCase is a GUI-testing tool, but not like any such tool you're likely to have seen before.. It aims to combine the ease of use of capture-replay tools with the maintainability of keyword-driven approaches.. It works on rich client UIs, and began life working only with PyGTK.. In recent years it has branched out and now also supports the Python libraries wxPython and Tkinter, and also Java SWT technology, including Eclipse RCP UIs.. Although making use of a recorder, it does not record the GUI mechanics directly, but allows the user to build up an extra layer of abstraction, essentially a Domain-Specific Testing Language.. Instead of an assertion mechanism, it generates a plain-text log of (in broad strokes) how the screen looks and how it changes in the course of the test: this information is then compared against previous runs of the same test.. This makes it both more responsive to change and easier for a non-programmer to use.. Acceptance Testing with Robot Framework.. Janne Härkönen and Pekka Klärck.. Robot Framework [1] is a generic test automation framework for acceptance testing and acceptance test-driven development (ATDD).. It has easy-to-use tabular test data syntax and utilizes the keyword-driven testing approach.. Its testing capabilities can be extended by test libraries implemented either with Python or Java.. Users can also create new higher level domain specific keywords from existing ones using the same syntax that is used for creating test cases.. In this session we demonstrate how easily Robot Framework test cases can be created and how good reports you get after execution.. We start from scratch but still manage to create several easy-to-understand test cases for a simple web based application.. The tests utilize SeleniumLibrary [2], which is just one of the several ready made test libraries available for Robot Framework.. [1] http://robotframework.. org/ [2] http://code.. google.. com/p/robotframework-seleniumlibrary.. Team Learning.. Team Learning.. Factors affecting Effectiveness of Agile Usage – Insights from the BBC Worldwide Case Study.. Mali Senapathi, Peter Middleton and Gareth Evans.. The past decade has seen significant changes in systems development with many organizations adopting agile methodologies as a viable methodology for developing systems.. An increasing number of research studies reveal the growing popularity and acceptance of agile methodologies.. While most academic research has focused on adoption and adaptation of agile methods, there is very limited understanding of their post-adoption usage and incorporation within organizations.. Have they been used effectively in the development of systems? What factors explain the effective usage of agile methodologies? A synthesis of past research in Systems Development Methodologies, Information Systems implementation, Diffusion of Innovations, and Agile Methodologies was conducted to develop a research model that identifies the main factors pertinent to the propagation and effective usage of agile methodologies in organizations.. The model is validated by applying it to the usage of Kanban for Software Engineering practices at BBC Worldwide, London.. Insights gained from the case study are discussed.. Learning about learning with the Dreyfus Model.. Patrick Kua.. (Lightning Talk, 10 min) [.. Learning is the bottleneck in software development.. We rarely get to work on the same problem twice.. Accelerating your ability to learn enables you to rapidly master skills and the Dreyfus Model of Skills Acquisition helps you understand how.. In this lightning talk, we'll cover the origins, applicability to software and agile techniques and how best to speed up your learning.. An amazing Dinner needs a Cookbook, a Chef AND a Kitchen.. Olaf Lewitz.. To become more agile in the enterprise, all people require dependable access to up to date, linked up, transparent information.. I outline some typical situations from my practical experience and the feedback I got in facilitating this topic as a presentation and workshop at three different conferences last year (HSE workshop, Munich, Scrum-Day, Berlin, XPDays Germany, Hamburg).. How can agile projects be integrated into the enterprise information infrastructure? How do we get away from storing Office documents on file servers? How does information from a whiteboard get into those documents, and vice versa? How does the infrastructure (of the projects and the enterprise) need to change to enable a sustainable integration? I’ll share experiences, point out typical traps and sensible solutions.. How do we make it work in practice, to change the enterprise information infrastructure in a way that it becomes useable as a base for agile process improvements? Mail: olaf.. lewitz@agile42.. com, Web page: http://www.. agile42.. com, Twitter account: @agile42 or @OlafLewitz.. "Discussion on the topics raised in Kati's talk with title "When agile is not enough".. "Discussion on the topics raised in Kati's talk with title "When agile is not enough".. Discussion on the topics raised in Kati's talk with title "When agile is not enough".. Experience Report.. Experience Report.. Agile Technical Management of Industrial Contracts: Scrum Development of Ground Segment Software at the European Space Agency.. Rui Santos, Felix Flentge, Marc-Elian Begin and Vicente Navarro.. (Experience Report, 30 min) [.. ESOC (the European Space Agency’s Operation Centre) is experimenting with Agile and Scrum methodologies in its quest for improving productivity, enhancing project visibility and control, reducing time to market, improve software quality and increasing user satisfaction.. In this article we present lessons learned from applying Agile in general and Scrum in particular to a number of projects, from applying a few Agile best practices to full Scrum.. ESOC has traditionally developed its software using a waterfall process mostly under Firm Fixed Price contracts, in this context using Agile brings challenges from project management, contracts and quality control perspective.. Using a coaching approach, the organisation has managed to accelerate its integration of Scrum, including industrial teams developing the software, and already yields positive results which are promising for the future.. Evolution of Longer-Term Planning in a Large Scale Agile Project – F-Secure’s experience.. Gabor Gunyho and Juan Gutierrez.. Many publications in the Agile literature offer ready-made “recipes” for solving a certain problem.. We believe this is way too often not helpful as the context varies a lot.. Instead we offer a _story_.. This is how _we_ did it in a big project.. The story is told through the major events of the project, called “Release Planning” events.. We hope that from our story you’ll learn some ideas on project planning and steering on a larger scale … even if it’s not promising to solve your problems ;-).. The release planning method itself (based on Dean Leffingwell's Agile Release Train) is explained on a high level only (one big picture).. Then we'll explain our journey with this method in a mid/big-size project (ca 120 people).. We explain how the long-term planning method evolved over the course of the "Business Iterations", a higher-level cycle on the timeline that business managers are interested about.. Several tough decisions had to be made as the project unfolded, from re-scoping to splitting the project.. We gained better understanding of the sheer size of the content, the inherent complexity of the product and the challenges of the multi-team setup with the help of this method.. We believe that without this added layer of planning many of these decisions could have happened very much later.. Our case is an example on gaining visibility to project progress on a higher level and getting better chances of steering a complex and risky project.. Harvesting the Net about Agile: Hot topics, influencers, Opinions, fears and solutions.. Paradigma.. Harvesting the Net about Agile: Hot topics, influencers, Opinions, fears and solutions: We will talk about the agile hot topics currently more commented in the Net like: UX-Agile, TDD and BDD problems, difficulties implementing scrum, agile and closed contracts and so on.. We will try to show the opinions and fears about them in Internet, twitter, to analyze the data and offer the best solutions/approaches to this topics.. 13:05-14:30.. 14:30-15:30.. Kanban.. Kanban.. The Principles of Kanban.. This talk will (quickly in 10 minutes) explain the Principles of the Kanban Method as detailed in this blog post http://agilemanagement.. net/index.. php/site/the_principles_of_the_kanban_method/ It will explain the principles of evolutionary change.. The 5 core practices and the 9 recognized emergent behaviors observed with teams pursuing the approach.. This is intended as a foundational talk for those who want to understand the theoretical framework of Kanban.. Studying Lean-Kanban approach using software process simulation.. David Anderson, Giulio Concas, Maria Ilaria Lunesu and Michele L.. We developed an event-driven simulator of the Kanban software process – a WIP limited pull system visualized by the Kanban board.. The simulator is fully object-oriented, and its design model reflects the objects of the Lean software development domain.. We used this simulator to assess comparatively WIP-limited and unlimited processes.. We also studied the optimum values of the working item limits in the activities, using a paradigmatic case of 4 activities and 100 work items.. The cost function used is equal to the total time needed to complete the project, plus a weighted sum of the limits themselves.. We performed an exhaustive search on all the admissible values of the solution, finding sensible optimal values, and a non-trivial behavior of the cost function in the optimization space.. This demonstrates the feasibility and usefulness of the approach.. 7 ways to sabotage your Kanban adoption.. Eelco Rustenburg and Erik van der Velde.. During our Kanban implementation at one of the biggest insurance companies in the Benelux we learned valuable lessons on what we could have done better the first time around.. The adoption included more than 15 teams and more than 150 people.. A Kanban adoption is different from an agile adoption.. The lessons learned are presented in a top 7 list.. Learn from our mistakes, so you don't have to make them.. Demos on Behaviour Driven Javascript and Functional programming in Clojure.. Demos on Behaviour Driven Javascript and Functional programming in Clojure.. Behaviour Driven Javascript.. Marcus Ahnve.. After the excellent presentation at last years XP2010 presentation on test driven Javascript in the browser, I have used the techniques proposed in real world code and expanded it to include the ideas from Behavior Driven Development.. My initial use of test driven Javascript very much followed my learning curve in other languages, i.. e.. first a very technical approach where test code actually tests a function.. Later, with a change of tools, I learned how to drive the code from actual behavior in the web page, instead of low level technical specs for a function.. The talk will shortly describe the journey from novice TDD Javascript to a more mature BDD approach.. It will have live coding showing examples from both approaches focusing on the BDD part, showing how the behavior of a web page is described in a BDD fashion and how it drives the implementation.. The  ...   With It?.. Rashina Hoda, James Noble and Stuart Marshall.. Self-organizing Agile teams need a supportive environment to emerge and flourish.. Through a Grounded Theory study of 58 Agile practitioners across 23 different software organizations in New Zealand and India, we found that senior management support is a critical environmental factor influencing self-organizing Agile teams.. We describe the influence of senior management, and show how their support can create and sustain a supportive environment for self-organizing Agile teams.. Treat them as addicts: drop Command And Control and embrace coaching with a 12 steps program.. Command and Control has many forms and names (old style management, micromanagement, consulting mode, military discipline) and all of them have been recognized as an anti-pattern for the emergence of complex, adaptative, cross-functional, self-organized teams that are capable of the kind of results that are not available through the sum of individual contributions.. Despite the overwhelming evidence against command and control on an Agile environment, the apparent easiness of the “just give’em hell and ask for more” method and it’s misleading occasional results provide all the environmental needs for the development of an addiction to power and the compulsory behaviors that result from this addiction.. In this lightning talk we will depict Command & Control managers as addicts, and we’ll see how a 12 steps program can help recover this individuals and place them on a path of facilitation, mentoring and coaching.. This steps, base on the famous AA program, should provide a method that allows the addict to admit that he can’t control his addiction, recognize that there’s a higher state of performance that it’s not possible right now, examine past errors in search of improvement opportunities, plan for improvement, develop a new code of behavior and help others that suffer from the same addictions.. Agile methodologies, Human Essence and the New Socialism.. Rafael Viveiros.. Why agile methodologies works well? What is the link and the key of sucess between agile methodologies and the new socialism? How ours attitudes as human beings make this things work well? How does this changes our lifes, our way to work and interact with employers and employees? What did those important and great Socialist thinkers say about? Is this the new socialism?.. Pair Programming: Demo and Report.. Pair Programming: Demo and Report.. Code craftsmanship in practice.. Johannes Brodwall and Ivar Nilsen.. At XP 2010, Ivar and Johannes demonstrated how fast a pair programming team can write a web application test first.. At XP2011, in the second installment of the Java EE spike kata, we demonstrate how to extend a simple test-driven web application and refactor from a simple to a more advanced design.. The demonstration starts with a small and simple existing code base.. We will add a requirement to this code base and test-drive the implementation.. In the course of the presentation, we will demonstrate effective pairing, several TDD techniques and libraries, effective use of Java IDEs and a complex refactoring.. The demonstration will take about 20 minutes, leaving plenty of time for questions.. Elements demonstrated: Effective pair programming; Test-driven development approaches; WebDriver, Mockito and FEST-assert as testing tools; How to test web applications via HTTP and by mocking the Java Servlet API; Refactoring techniques - Replace Method with Method Object.. Why you should care? Because XP practices are easy to talk about but hard to do; Get inspiration for attacking your own problems with tests Get inspiration for how to pair effectively and have more fun!.. Who should watch? Developers with limited experience with XP coding techniques and their bosses; Developers who wonder how to apply XP techniques in realistic projects; Developers who want to see how much a modern IDE really can do for you; Project managers who wonder what it will be like if their projects use these techniques.. Pair Programming and Software Defects – an Industrial Case Study.. Nattakarn Phaphoom, Alberto Sillitti and Giancarlo Succi.. In the last decade there has been increasing interest in pair programming.. However, despite work has been done, there is still a lack of substantial evidence of pair programming effects in industrial environments.. To increase a body of evidence regarding the real benefits of pair programming, we investigate its relationship with software defects.. The analysis is based on 14-months data collected from a large Italian manufacturing company.. The team of 17 developers adopted a customized version of extreme programming and used pair programming on a daily basis.. We explore and compare the defect rate of the code changed by doing pair and solo programming.. The results show that defects appear to be lower for the code modified during pair programming.. As a consequence, we formulate a hypothesis that pair programming is effective in reducing the introduction of new defects when existing code is modified.. Discussion: Acceptance Test Driven Development and Behaviour Driven Development.. Expert panel discussion about Acceptance Test Driven Development and Behaviour Driven Development.. Facilitator: Emily Bache.. Other panelists: Elizabeth Keogh, Pekka Klärck, Marcus Ahnve, JB Rainsberger.. What are the benefits of doing BDD or ATDD over just unit testing? How do you know if you are doing BDD or ATDD right? What are the most common mistakes teams make? - these are just some of the questions this panel of experts will be answering in this session.. All conference participants are welcome to come and contribute questions and listen to the discussion.. A Case Study in “Agile at Scale” Delivery.. Alan Brown.. Many individuals and teams involved on projects are already using agile development techniques as part of their daily work.. However, we have much less experience in how to scale and manage agile practices as part of a concerted effort of improvement across an integrated supply-chain for enterprise software delivery.. In this paper we discuss the scalability of agile approaches through a detailed case study in agile adoption.. In the context of this example we examine how “agility at scale” is applied, describe the key scaling factors and their impact on agility, and review some of the rollout and deployment issues that can limit the adoption of agile approaches in practice.. A Never Ending Battle for Continuous Improvement.. Juanjuan Zang.. This paper takes the readers through a real project life path to show what went well and what didn’t.. The paper first lays out all the pain points of the project.. Then it describes how the team has successfully handled each of the issues.. The paper doesn’t stop here.. Instead, it digs further by taking off the veil of success as the project looks like and focuses on the areas needing improvement.. The paper elaborates on how to squeeze out nonvalue-added waste through value stream mapping.. It also discusses the importance of Agile “transfer”, customer redefinition as well as running a true iterative iteration.. Pair Programming.. Pair Programming.. Analysing the usage of tools in pair programming sessions.. Ilenia Fronza, Alberto Sillitti, Giancarlo Succi and Jelena Vlasenko.. Pair Programming is one of the techniques of agile methods that has gained popularity both in academic and industrial environment.. Many advantages and disadvantages of this technique have been identified.. In this study we observe daily work of nineteen software developers of a large Italian manufacturing company for a period of ten months.. Fifteen developers are existing team members and four have recently joined the team.. We identify the tools the developers use, how they distribute their time among these tools when working alone and when doing Pair Programming.. The data has been extracted non-invasively by means of PROM – tool for automated data collection and analysis.. The preliminary results indicate that the developers working in pairs in all configurations devote significantly more time to programming activities than the developers working alone.. Collaboration in Pair Programming: Driving and Switching.. Laura Plonka, Judith Segal, Helen Sharp and Janet van der Linden.. This paper reports on an empirical study about the mechanisms of collaboration of drivers and navigators in Pair gramming (PP) sessions.. Based on video recordings of professional software developers, we analysed the mechanisms of role switches and how developers split the task of driving.. We found that developers do not evenly contribute to the task of driving and that they spend on average a third of the session without any computer interaction focusing mainly on communication.. In addition, our results show that most pairs switch roles frequently and that the frequency and fluidity of switches indicate the high level of engagement on the part of both developers.. Leadership.. Empirical Investigation on Agile Methods Usage: Issues Identified from Early Adopters in Malaysia.. Ani Liza Asnawi, Andrew M Gravell and Gary Wills.. Agile Methods are a set of software practices that can help to produce products faster and at the same time deliver what customers want.. Despite the benefits that Agile methods can deliver, however, we found few studies from the Southeast Asia region, particularly Malaysia.. As a result, less empirical evidence can be obtained in the country making its implementation harder.. To use a new method, experience from other practitioners is critical, which describes what is important, what is possible and what is not possible concerning Agile.. We conducted a qualitative study to understand the issues faced by early adopters in Malaysia where Agile methods are still relatively new.. The initial study involves 13 participants including project managers, CEOs, founders and software developers from seven organisations.. Our study has shown that social and human aspects are important when using Agile methods.. While technical aspects have always been considered to exist in software development, we found these factors to be less important when using Agile methods.. The results obtained can serve as guidelines to practitioners in the country and the neighbouring regions.. Coaching at the right level with Miracle Mountain.. Patrick Verheij.. Do you ever struggle while addressing motivational issues with your people? Do you ever wonder how to improve the performance of your teams? Managers and coaches now get a chance to meet Miracle Mountain, a model for more effective coaching.. This 5-level model is a powerful management and coaching tool to find the root cause of problems and the core of improvement opportunities.. The true power of the model lies in the fact that it helps you address the intrinsic motivation of people and make them work miracles.. During this lightning talk, you will be introduced to the model and be guided to using it effectively.. Help people work miracles with Miracle Mountain in your backpack.. 10 things to drive your ScrumMaster crazy.. In my life as ScrumMaster I faced many things which drove me nuts.. In my lightning talk I will speak about the 10 best things to drive YOUR ScrumMaster crazy.. Agilyze them!.. Rafael Flores, Raúl Sanz de Acedo, Asun Ayesa and Carlos Urtasun.. "Experiences on promoting Agile Methodologies in our Region".. This talk will be different from most because we will not talk about an idea but rather about a project we run last year 2010 on our Region in Navarre in order to promote the adoption (and use) of Agile Methodologies in any kind of development project (IT or not).. We will talk (fast, promised!) ahout why we did it, how we did it, what outcomes we've had so far as well as show briefly our future (next Sprint) plans, which could greatly benefit with the ideas and contributions of any of the attendants.. We think it can be a nice experience to share, this is the purpose of this Lighting Talk.. Discussion by Jutta Eckstein: Agile at Scale (Fishbowl).. Discussion by Jutta Eckstein: Agile at Scale (Fishbowl).. Agile at Scale (Fishbowl).. Facilitator: Jutta Eckstein.. Other panelists: Mary Poppendieck, Gabor Gunyho, Juan Gutierrez, Alan Brown, and Eelco Rustenburg.. Ten years ago, at the time the Agile Manifesto has been created, most people believed that agile software development is for small projects and teams only.. With the overall success of agile approaches more and more large projects, teams, and organizations also wanted to benefit from a value system that is helpful for small projects.. Although in the meantime we’ve made many experiences applying agile in a large context it is still true that agile at scale differs from agile at small, because of the difference in constraints.. We will discuss experiences and still open issues with agile at scale in a fishbowl, which is an open discussion for every participant.. Thus, join the fishbowl and involve yourself in the discussion with speakers and other participants.. Invited talk by Laurent Bossavit: Forty years of software engineering, ten years of Agile, now what?.. Forty years of software engineering, ten years of Agile, now what?.. Laurent Bossavit.. The software profession appears largely ignorant of its own history, an ignorance which has detrimental consequences.. This beginner-friendly talk goes back to the forty-year old roots of "software engineering" and the "software crisis" and applies the model of "disruptive innovation" to clarify where Agile has come from and where it is headed.. It debunks some Agile myths along the way, such as "Agile has gone mainstream" and the push for more certification, outlining an alternative roadmap for progress driven by the Agile community.. Friday, 13 May 2011: Workshop / Tutorial Day.. Refactoring in the 4th Dimension (Workshop) by Michael Feathers.. Refactoring in the 4th Dimension (Workshop) by Michael Feathers.. It is clearly as important as the other three dimensions but we don't often think about it because it is not in front of our eyes.. Time presents the same problem in refactoring.. We see the current structure of our code, but what we don't see in front of us is its history.. We make assumptions about how changes occur based upon conception tools like the Open/Closed Principle, but we can make our decisions based on actual data.. After all, we have version control histories of our code.. We will also discuss how what we've learned can inform and affect our reasoning about refactoring.. Acceptance Test Driven Development (ATDD) with Robot Framework (Tutorial) by Pekka Klärck and Janne Härkönen.. Acceptance Test Driven Development (ATDD) with Robot Framework (Tutorial) by Pekka Klärck and Janne Härkönen.. Pekka Klärck and Janne Härkönen.. Requirements in general, and executable requirements in particular, are important for all project members (customers, developers, testers,.. ) and this workshop has something to offer to all these stakeholders.. The workshop is suitable for both practitioners and beginners.. Beginners will get a deep introduction of executable requirements and see how the process works.. Practitioners can deepen their knowledge, share their experiences and learn from others.. Workshop starts with a short introduction of executable requirements and Acceptance Test Driven Development (ATDD) process.. The ATDD workflow, Discuss–Develop–Deliver, is explained to provide frame for rest of the session.. Additionally Robot Framework, the tool that is used to automate executable requirements, is briefly introduced.. The hands-on part starts by introducing an existing, partially complete application which will be developed further during a mini-iteration.. Existing acceptance tests and the development environment are introduced to show how development has been conducted earlier.. We will also briefly discuss version control and continuous integration, two important pieces of the whole ATDD workflow, and participants will see these tools also in action.. The actual hands-on iteration begins with the Discuss phase.. The target is to gain collaborative understanding about what we want to build and document that as executable examples.. This is the most important phase of the ATDD process and also the most important learning possibility in this tutorial.. In the Development phace the participants automate the executable examples using Robot Framework together with the organizers.. The organizers act as developers and are responsible for implementing the new features.. Although we use Robot Framework for automation, everything related to ATDD process itself is generic.. No previous experience about ATDD or Robot Framework is expected, but basic understanding of Agile practices is assumed.. What's in your coaching backpack? (Workshop) by Patrick Kua.. What's in your coaching backpack? (Workshop) by Patrick Kua.. Come along with your favourite coaching models, references and tools to share and make room in your backpack to add some new things to take away.. thekua.. com/atwork.. The Fit of Software Development in the Larger Organization (Tutorial) by Mary Poppendieck and Tom Poppendieck.. The Fit of Software Development in the Larger Organization (Tutorial) by Mary Poppendieck and Tom Poppendieck.. Mary Poppendieck and Tom Poppendieck.. Building the Right Thing – How does the software development organization fit into the overall company and provide the capabilities that are most critical to the company’s success? 2.. Leadership – A Product Manager is an outward facing role, while a Product Owner is an inward-facing role; can one person manage both roles? 3.. Design Thinking – Dealing with complexity is the essence of software development; how does design thinking help manage complex environments?.. Silo Busting (Tutorial) by Tom Perry and Lourdes Vidueira.. Silo Busting (Tutorial) by Tom Perry and Lourdes Vidueira.. Tom Perry and Lourdes Vidueira.. Organizational silos are the source of the most pernicious dysfunctions you can find within any company.. These divisions serve to isolate people in the organization within hyper-specialized roles.. Ostensibly, we do this in order to help people succeed.. The Justification might be that no one can be equally good at everything.. Therefore, we compartmentalize our lives and those around us in order to filter out the extraneous noise.. Of course, it does not have to be this way.. You can deliver a product successfully without compartmentalizing everyone and everything in an organization within an inch of its life.. It requires a different mindset.. One needs inter-disciplinary thinking that considers different skills and tries to synthesize a whole rather than divide.. This requires a mindset that favors skill over roles and knowledge over assignment.. As teams, we need to have the proper balance of skills, including development, quality assurance, customers, and delivery.. Moreover, as an organization, we need to have the people in place to help support the teams and the people on the teams to develop themselves and to deliver the best products.. You Get What You Measure (Tutorial) by Ravindar Gujral and Andre Dhondt.. You Get What You Measure (Tutorial) by Ravindar Gujral and Andre Dhondt.. Ravindar Gujral and Andre Dhondt.. Metrics, when they are used at all, serve organizations as a way to understand where project teams stand.. When it comes to software development, however, these mechanisms can sometimes backfire.. As adoption of lean/agile practices and methods becomes more prevalent, organizations struggle with finding the right measures to understand team adoption and progress.. In this presentation we will show that what we measure (about teams or individuals) can cause sub-optimal behavior--by beginning the session with a paper-and-scissors snowflake manufacturing game.. Part I: Why Measure? 45 minutes Snowflake Manufacturing Teams • break into groups of five, reserving one team to play the role of "client" • alternating teams get rigid process rules or self-organizing team rules • teams are given 5 minutes to produce as many snowflakes as possible • now teams take their snowflakes to market, and see if the "clients" will buy • group retrospective: we find out that only "beautiful" snowflakes sell, and we have a lot of waste! (beautiful is defined in the client instruction page) • shuffle teams, then iterate again, with a new objective: produce the most snowflakes that are also beautiful enough to sell Part II: What Measurements are Useful? 45 minutes Why We Measure • Quantify where we are and what we need • To share best practices • Benchmarking to determine the effect of change Popular metrics (and pitfalls) • Size of code/LOC (Line of code) • Code coverage • Unplanned feature Change • Schedule and Budget Compliance • Cycle Time • Velocity (story points or story count per sprint) • Defect count (at various phases) • Return on investment • Innovations per sprint / slack time • Artifacts generated • Function points Standard Work • Taiichi Ohno says standards should be challenged constantly • Let individuals/teams define standard work so that they feel ownership.. Supporting Kaizen • Metrics are to be short-lived: set a goal, define a metric, make changes and gauge whether you're going in the right direction.. Discard the metric once your goals are met.. • Like statistics, all metrics lie--they are a limited view of the whole story, so don't take them too seriously.. Use them as indicators for further investigation.. • While metrics appeal to our logical/quantitative side, not all things can be measured--and some of the most important things are not measurable.. Keep a view of the whole system, and value qualitative attributes of our work too! Part III: Beyond Metrics: Get What You Really Want (90 minutes) A Brief History of Management for Knowledge Workers As Peter Drucker says, the most difficult part of management is figuring out what our goals should be.. Along the same vein, Russell Ackoff says "it's better to do the right thing wronger than the wrong thing righter.. " XP has taught us to take baby steps, to move iteratively so we can get feedback before we go too far in the wrong direction.. The Lean Startup community has pushed this to yet another extreme by finding ways to get feedback before even building a product.. How to Build What The Customer Wants • Validated Learning > Working Software > Comprehensive Documentation • Baby Steps > Big Steps • End-to-end > optimizing subsystems • Self-organization > binding objectives • Team Ownership of Product > Proxy Client / Product Owners • Soft-spokenness, modeling, and coaching > High-pressure management • Smaller teams > bigger teams • Simplicity > Complexity Focus and effectiveness • Team synch points • Managing energy instead of time • Product Road Maps The Lean/Agile Treadmill • Busy, busy, busy == never get anything important done • Slack creates disruptive change == creates value • Product success makes the product obsolete (c.. f.. Drucker: trains -> Ford's Model T -> GM) • The most value comes from our links to people / ideas outside our context (c.. Block: social capital) • Are we going to sprint all iteration long? The Power of Positive Modeling • Growing your influence: applying Weinberg's Law of Raspberry Jam -- small meetings! • Idea farming: planting seeds and watch them grow • Peer Feedback • Keeping it Light • Making Work Fun / Playful • All this gives you teams that go above and beyond!.. Extreme Startup (Workshop) by Robert Chatley and Matt Wynne.. Extreme Startup (Workshop) by Robert Chatley and Matt Wynne.. Robert Chatley and Matt Wynne.. In this hands-on workshop we aim to simulate product teams building software and delivering it into a market.. The earlier you release your software, the sooner you will start accruing points, and the earlier you can learn something about the market, which should inform your next iteration.. In the lean startup movement, this is know as the Build-Measure-Learn cycle[6].. The aim of the workshop is to simulate product development in a quickly changing environment, where agile techniques should excel.. How quickly can we iterate? What are the bottlenecks? Which techniques are most valuable? Do any fall by the wayside? Robert Chatley.. http://chatley.. http://develogical.. Matt Wynne.. mattwynne.. net/.. Value-Based Software Traceability (Workshop) by Angelina Espinoza, Richard Paige and Juan Garbajosa.. Value-Based Software Traceability (Workshop) by Angelina Espinoza, Richard Paige and Juan Garbajosa.. Angelina Espinoza, Richard Paige and Juan Garbajosa.. Traceability provides an essential support for developing high quality software systems.. Traceability, therefore, has been traditionally strongly infuenced by the software process drivers.. However, the software process is, during the last few years, considering new drivers.. One of them is value.. The global value of a product can be understood as the perceived benets in relation to its cost.. However, the technical and business stakeholders need a close interaction to consider each other in their product value management approaches, otherwise business decisions would not consider software engineering impacts and vice versa, development decisions would not take into account business value requirements.. From the perspective of traceability, the value consideration may change many assumptions.. Traceability items should contain the necessary information to estimate its value under a given context.. Therefore the traditional traceability schemes seem to be too limited for describing and tracing the value.. To start with, it would be necessary to understand the scope, delivery and implications of value tracing.. Additionally, the agile community claims for a trustworthy transparency over tiresome traceability in order to get projects which are transparent and visible in their status/accounting.. Then, these traceability approaches need to provide, what is called by some authors, lean traceability.. Therefore, the VALSOT workshop's main objectives are: 1) to create a forum to discuss current approaches on software value-based traceability, 2) to state a research agenda based on the above topics, highly oriented to support industrial contexts.. How complex is software development? (Workshop) by John Mcfadyen.. How complex is software development? (Workshop) by John Mcfadyen.. John Mcfadyen.. There are terms used in the agile software world that have their origins in complexity science, terms such as self-organisation and emergence.. The problem is that when these terms are used it isn’t always correctly.. uk Web:.. Twitter: @johnmcfadyen.. Agile Management: Leading Agile Developers (Workshop) by Jurgen Appelo.. Agile Management: Leading Agile Developers (Workshop) by Jurgen Appelo.. Agile Management: Leading Agile Developers.. (Workshop, 3 hour) [.. Agile management is an often overlooked part of Agile.. There is much information available for agile developers, testers, and project managers, but very little for development managers and team leaders.. However, when organizations adopt agile software development, not only developers, testers, and project managers need to learn new practices.. Development managers and team leaders must also learn a new approach to leading and managing agile organizations.. Several studies indicate that “old-style” managers are the biggest obstacle in transitions to agile software development.. Development managers and team leaders need to learn what their new role is in agile software development organizations.. This workshop will help them.. The same workshop was held for the first time at the Scrum Gathering in Amsterdam in November.. It was the most popular session, with the most attendees, and excellent evaluations.. Most of the workshop is based on the new book "Management 3.. 0", published in January 2011 in Mike Cohn's Signature Series.. management30.. com/book/.. Introduction to Behaviour Driven Development (Tutorial) by Liz Keogh.. Introduction to Behaviour Driven Development (Tutorial) by Liz Keogh.. Liz Keogh.. BDD is a set of practices which help software development teams to have conversations about the behavior of their system and how it delivers value to the project stakeholders.. BDD has changed from its early roots as a replacement to TDD and now works as a mini-methodology across the whole software lifecycle.. Over the last few years the adoption of BDD has grown globally, with dozens of tools created, used by hundreds of projects around the world.. , In this tutorial we look at the original reasons behind the creation of BDD, bringing the focus back to the language and conversations which lie at its heart.. We look at how BDD’s patterns can be applied at multiple scales – from the initial project vision all the way to the code – to deliberately discover and address ignorance in every aspect of software development, producing reliable, maintainable software that matters.. , , Attendees will learn:, , • The origins of BDD and the problems it solves, • Why ignorance is the constraint on your project, • Some frequently used conversational patterns, • How BDD can be applied from analysis to code, • How to use BDD tools effectively, • How to adopt BDD incrementally on a project, and which aspects are most important, • How to create a safe learning environment in which BDD can thrive.. Retrospectives in action (Tutorial) by Patrick Kua and Nick Oostvogels.. Retrospectives in action (Tutorial) by Patrick Kua and Nick Oostvogels.. Patrick Kua and Nick Oostvogels.. At the heart of agile and lean thinking is the idea of change for the better.. One small improvement every day is another step towards continuous improvement.. In many agile teams, retrospectives are the key enabling practice to continuous improvement yet it’s often difficult to understand what an effective retrospective feels like, and what elements teams should strive for.. , , This tutorial offers something for everyone to learn how to use retrospectives to foster a culture of continuous improvement.. Experienced people will refine their understanding through our exploration of the key elements and widen their toolkit by two experienced and passionate retrospective facilitators.. , , More importantly this tutorial encourages the most effective learning by involving all participants in a series of exercises to experience what an effective retrospective might feel like.. , , Participants will come away having learned:, - The key elements of a retrospective, - The responsibilities of the facilitator, - A set of exercises to be used throughout a retrospective, - The pitfalls and remedies when retrospectives go wrong, , No prior experience is required to participate in this tutorial..

    Original link path: /program/
    Open archive
  •  

  • Title: Organization
    Descriptive info: General Chair.. Rachel Davies.. Agile Experience Ltd, UK.. XP Steering Committee Chair.. Germany.. Organizing Co-Chairs.. Juan Garbajosa.. UPM, Spain.. Agustin Yagüe.. PC Co-Chairs.. Philippe Kruchten.. U.. of British Columbia, Canada.. Juan Garbajosa.. Research Program Co-Chairs.. Orit Hazzan.. Technion, Israel.. Alberto Sillitti.. Free University of Bozen Bolzano, Italy.. Workshops Co-Chairs.. Lasse Koskela.. Reaktor Innovation Finland.. Xiaofeng Wang.. Lero, Ireland.. Tutorials Co-Chairs.. Xavier Quesada.. Agilar, Argentina.. Ralph Miarka.. Independent, Austria.. Doctoral Consortium Co-Chairs.. Yael Dubinsky.. IBM, Israel.. Jennifer Pérez.. Industry Program Co-Chairs.. Bache Consulting, Sweden.. Xavier Albaladejo.. Everis,  ...   Talks Co-Chairs.. Naresh Jain.. Industrial Logic, India.. Rodrigo Corral.. Plain Concepts, Spain.. Open Space Co-Chairs.. Charlie Poole.. Poole Consulting, USA.. Agustín Yagüe.. Publicity Co-Chairs.. Steven Fraser.. Cisco Research Center, USA.. Hironori Wazisaki.. Waseda University, Japan.. Local Arragements Co-Chairs.. Jessica Díaz.. Sponsorships Co-Chairs.. Jorge Uriarte.. Gailen, Spain.. Int.. Volunteers Program Co-Chairs.. Angelina Espinoza.. SivaKumar Dorairaj.. Victoria University of Wellington, New Zealand.. Conference profile design by Mattis Storhaug, Kantega and conference webpage by Eirik Bjørsnøs, Kantega.. We would like to thank the following organizations that have supported the conference:..

    Original link path: /content/6/Organization
    Open archive

  • Title: Venue
    Descriptive info: Restaurant.. Colonial de Mónaco.. Bus Departure From Hotel NH Parque Avenidas at 19:30.. Read More.. Conference Hotel.. NH Parque Avenidas ****.. Calle de Biarritz, 2.. 28028 Madrid (Spain).. Tel.. +34.. 91.. 3610288 | Fax: +34.. 3612162 | E-mail:.. nhparqueavenidas@nh-hotels.. With a great location in the Salamanca neighborhood near the Plaza de Toros de las Ventas, and ease of access to the M-30 and the airport.. web site:.. nh-hotels.. com/nh/en/hotels/spain/madrid/nh-parque-avenidas.. html.. LAST MINUTE INFORMATION (.. Download.. IBERIA, L.. A.. E.. Operator :..  ...   (OW/RT):.. Domestic, European and Intercontinental Flights:.. 45%.. discount on full.. Business.. Class fares.. 50%.. Economy.. These conditions refer exclusively to confirmed (except Shuttel Flights) IBERIA and AIR NOSTRUM flights (no codeshare flights IB-7000- 4000 and 5000), travelling from 2 days before to 2 days after the Event for Domestic and European flights, and from 7 days before to 7 days after for Intercontinental flights.. These tickets can be issued either by IBERIA Ticket Offices, IBERIA's website.. (www.. iberia.. com/ferias-congresos).. and SERVIBERIA..

    Original link path: /content/201/Venue
    Open archive

  • Title: Photo Gallery
    Descriptive info: Check out here, the lastest photos taken in the conference.. Daily updated.. Madrid.. Tuesday.. More.. here..

    Original link path: /content/206/Photo-Gallery
    Open archive

  • Title: Videos
    Descriptive info: Videos available.. Session 1: Keynote by Esther Derby:.. Session 2: Esther Derby keynote + Invited Talk by Kati Vilkki: When agile is not enough.. (.. dowload.. Session 3: Invited talk by Jurgen Appelo.. Session 4: Invited Talk by Angel Medinilla: Scrumban.. Session 5: Keynote by Brian Marick:.. Session 6: Invited Talk by Mike Hill: Geek Leadership In Deep Legacy.. Session 7: Invited Talk by Elizabeth Keogh: BDD for Life: Using the Philosophy and Patterns in Coaching.. Session 8: Invited talk by Laurent Bossavit: Forty years of software engineering, ten years of Agile, now what?..

    Original link path: /content/208/Videos
    Open archive

  • Title: Changes in the program
    Descriptive info: Kati Vilkki's talk has been moved from Thursday 12th at 17:00 to Wednesday 11th at 11 (after the keynote).. You can also continue with the discussion at Barcelona meeting room at 12..

    Original link path: /content/205/Changes-in-the-program
    Open archive

  • Title: Conference Dinner
    Descriptive info: Colonial de Mónaco.. Address.. Avda.. Principal s/n.. Recinto ferial Casa de Campo.. Bus Departure.. From Hotel NH Parque Avenidas at 19:30..

    Original link path: /content/204/Conference-Dinner
    Open archive

  • Title: Last minute information
    Descriptive info: Download the file from..

    Original link path: /content/203/Last-minute-information
    Open archive

  • Title: Program printed version available
    Descriptive info: You can download the final version of the program with all the useful information of XP2011..

    Original link path: /content/202/Program-printed-version-available
    Open archive



  •  


    Archived pages: 158