|
|
|
|
|
| |
|
| Alan Shalloway, Net Objectives |
 |
As the popularity of agile development spreads, more and more companies are discovering that simply breaking down projects into small iterations is not sufficient. Agile methods require changes in management, analysis, architecture, design, testing, and quality assurance, as well as project management. Given the substantial adjustments required, where can a team or enterprise look for guidance in its transition? Learning the required skill sets individually is fraught with problems—analysis, design, code, and test are not independent; they must be integrated. Join Alan Shalloway as he describes the landscape of skills that a development team needs to become effective agile developers. He discusses a set of principles and practices that integrate the guidance provided by lean, agile methods, design patterns, and more. In particular, Alan details how agile analysis and design patterns support agile methods, and how core Lean principles support all agile methods, including design and test-driven development.
|
| Alan Shalloway is the founder and CEO of Net Objectives. With more than thirty-five years of experience, Alan is an industry thought leader, trainer, and coach in the areas of lean software development, the lean-agile connection, Scrum, agile architecture, and using design patterns in agile environments. He is a popular speaker at prestigious conferences worldwide as well as a trainer/coach. Alan is the primary author of Design Patterns Explained: A New Perspective on Object-Oriented Design and is currently writing a book on Lean Anti-Patterns. |
|
 |
|
|
| |
| |
|
This “on-your-feet” tutorial guides project managers, agile coaches, and Scrum Masters in how to apply facilitation techniques and tools to support collaborative decision making. These practices are critical for agile planning, daily interaction, and reviews of agile software development projects and teams. Jean Tabaka shows why agile teams require a collaborative style of decision making rather than classic command-and-control approaches. Practice planning for agile meetings and kicking off those meetings to ensure that the attendees are truly engaged and results-oriented. Find out about tools to help teams gather the important insights and wisdom necessary to attain the sustainable agreements in their agile projects. Learn ways to deal with conflict that occurs when many opinions and recommendations arise and help teams inspect and adapt their agile processes collaboratively. Along the way, you will discover what must change within your organization to successfully apply collaboration, especially with large and distributed agile teams.
|
| Jean Tabaka is an Agile Mentor and Coach with Rally Software Development. In addition to being a Certified Scrum Trainer and Practitioner, she is also a Certified Professional Facilitator. Her unique blend of passions and skills has been applied in a variety of organizations—large and small, co-located and distributed—eager to adopt the best of agile and bring out the best in their teams. Author of the Agile Software Development Series book Collaboration Explained, Jean holds a Masters in Computer Science from Johns Hopkins University. When not sharing her agile passion with clients, she resides in beautiful Boulder, Colorado. |
|
 |
|
|
| |
| |
|
| Ellen Gottesdiener, EBG Consulting |
|
Well-designed and well-run, facilitated requirements workshops are one of the best ways to establish your product roadmap, release strategy, and iteration requirements. Workshops can reveal not only user requirements but also quality attributes and technical infrastructure needs that are crucial to large or complex projects. You can use workshops to actively engage customers early in the project and provide a framework for making decisions about when and what to build. Join Ellen Gottesdiener as she presents a toolkit of practices and guidelines—reinforced with practice sessions and group discussions—that you can apply to improve the quality of your product development efforts. Take back a structured approach for a series of interwoven agile workshops—Product Roadmap, Release Roadmap, and Iteration Planning—to provide just enough requirements-related information at the right time for your next agile project.
|
| Principal Consultant of EBG Consulting, Ellen Gottesdiener helps business and technical teams get product requirements right so projects start smart and deliver the right product at the right time. She helps agile teams define their product and release roadmaps and elicit just enough requirements to achieve iteration and product goals. Ellen is the author of Requirements by Collaboration and The Software Requirements Memory Jogger. In addition to direct project consulting, Ellen writes articles, speaks at industry conferences, and provides seminars to clients. You can contact Ellen at www.ebgconsulting.com. |
|
 |
|
|
| |
| |
|
| James Coplien, Nordija A/S |
|
Architecture is a heavyweight activity, and the magic of agile makes it unnecessary to bother with up-front architectural design, right? Wrong! James (Cope) Coplien shows how to infuse just enough architecture in your first sprint to lay the foundation for both short-term success in GUI design/test and long-term success in reduced maintenance costs and increased feature velocity—all within the spirit of the Agile Manifesto. In your first sprint you create an architecture that focuses both on what the system is and what the system does. Creating interfaces that capture the essence of system form is lean-agile while laying a foundation for responsiveness to change. Cope’s agile architecture approach generates minimal documentation without tools and formal notations and provides a foundation of usability—a key ingredient missing from agile. This tutorial builds on expert experience and recent empirical studies proven to solve common agile development architecture and design problems.
|
| A Senior Agile Coach and Software Architect at Nordija A/S in Copenhagen, James Coplien is the co-author of Organizational Patterns of Agile Software Development. Cope's perspectives are grounded not only in extensive empirical research but also in his long-standing and ongoing work writing production software. His current endeavors include consulting on software architecture and organizational structure, agile readiness assessments, software usability consulting and training, and research into patterns for highly dynamic systems. James has never designed a programming language and has never created a methodology. |
|
 |
|
|
| |
| |
|
| Jutta Eckstein, IT communication |
|
Many people believe that agile software development is only for small teams. However, the agile value system and the principles behind it as stated in the Agile Manifesto do not say anything about team or project size. Jutta Eckstein’s work is typically with large, distributed, and mission-critical systems. Several years ago she took up the challenge and tried applying agile software development in the large—and it works! Large projects and even distributed teams can benefit from the same agile value system that is useful for small teams. Jutta discusses how to instill the agile value system in medium- and large-sized teams and how to coordinate agile projects with sub-teams in multiple locations. She shares her insights on the impacts of switching to agile, especially on establishing and preserving mutual respect between locations and how project size and team size influence the underlying agile architecture. Learn about the typical obstacles to applying agile in a large or distributed setting and practical approaches to overcoming these obstacles.
|
| A partner of IT communication, Jutta Eckstein is an independent consultant and trainer from Braunschweig, Germany. Her know-how in agile processes is based on more than ten years of experience in developing object-oriented applications. Jutta’s unique experience in applying agile processes within medium- to large-sized mission-critical projects is the basis of her book, Agile Software Development in the Large: Diving into the Deep. A member of the board of the Agile Alliance, Jutta has presented at conferences throughout Europe and the US. |
|
 |
|
|
| |
|
|
| |
| |
|
| Mike Cohn, Mountain Goat Software |
 |
Planning is important for all projects, including agile ones. Unfortunately, we’ve all seen so many worthless plans that we’d like to just throw planning out altogether. But let’s not give up yet. It is possible to create a project plan that looks forward six to nine months—and yet is accurate and useful. Too many teams view planning as something to be avoided, and too many organizations view plans as something to hold against their development teams. Mike Cohn describes how to break that cycle by acquiring new skills that help you to create reliable plans for improved decision-making. Leave this session with a solid understanding of and experience in agile planning. Mike presents various approaches to estimating, including unit-less points and ideal time. Participants also practice estimating with the popular Planning Poker technique. Together, you and Mike will explore techniques that dramatically increase your project’s chances of on-time completion.
|
| Mike Cohn is the founder of Mountain Goat Software, a process and project management consultancy and training firm. He is the author of Agile Estimating and Planning and User Stories Applied for Agile Software Development, as well as books on Java and C++ programming. With more than twenty years of experience, Mike has previously been a technology executive in companies of various sizes—from startup to Fortune 40. A frequent magazine contributor and conference speaker, Mike is a founding member of the Scrum Alliance and the Agile Alliance. He can be reached at [email protected]. |
|
 |
|
|
| |
| |
|
| Jeff Patton, ThoughtWorks |
|
Leveraging what you understand about your application’s users is central to a user centered design approach. User personas have been touted as a way to improve the quality of the user experience. But what exactly is a persona? How do you create one? And, how does a persona differ from other popular approaches to modeling users such as actors, user roles, or user profiles? In this tutorial you’ll discover how user models fit into a holistic user centered design process. Through discussion and practice you’ll learn about various types of user models and how to create simple role models, user profiles, and personas. Join Jeff Patton and learn how to leverage these user models to identify valuable features for your product. Learn new skills to help you discover the overarching design characteristics your product must have to be successful. This tutorial is fast paced, information dense, and full of collaborative activities to give you practice with the concepts and techniques introduced.
|
| Since 2000, Jeff Patton has championed the incorporation of User Centered Design (UCD) into both traditional and agile software development projects. Through his writing, teaching, speaking, and practice, Jeff works to introduce developers, analysts, product managers, and others to UCD techniques. Jeff is a consultant with ThoughtWorks, working in a wide variety of domains from healthcare to stock portfolio management. Jeff is currently a columnist for StickyMinds.com and IEEE Software. He’s at work on a book about incorporating UCD thinking into agile development. Visit Jeff’s website at www.agileproductdesign.com |
|
 |
|
|
| |
| |
|
Refactoring is a development practice well accepted both inside and outside the agile community. However, many myths and misconceptions surround refactoring. Some of these misconceptions have led to nightmares for project stakeholders. Naresh Jain helps you understand the real meaning and the correct use of refactoring. He provides an opportunity for you to explore these concepts in action through hands-on exercises using a real open source project. You’ll review a common refactoring vocabulary, learn to identify “code smells” and eliminate them by applying simple refactoring techniques, discover how to write better unit tests, understand some of the pitfalls in refactoring legacy code in the absence of usable tests, and take existing code and refactor it to use good design patterns.
|
Laptop Required |
|
|
This is complete hands-on session requiring you to bring your laptop loaded with JDK 5 or higher and your favorite Java IDE. Have your battery fully charged and be ready to go. |
|
| Naresh Jain is a software craftsman working as a consultant for ThoughtWorks India. He has worked on a variety of software projects utilizing XP, Scrum, and CMMI5i in India and the US. Naresh is the founder and vice-chairman of the Agile Software Community of India and the organizer of the Simple Design and Testing Conference (SDTConf). He has helped start various agile user groups including the Agile Philly User Group and several groups in India. By becoming part of a team, Naresh helps software companies embrace agile. Naresh enjoys beer, music, adventure sports, and hot food of any color. You can reach him at [email protected]. |
|
 |
|
|
| |
| |
|
| Esther Derby, Esther Derby & Associates |
|
Adopting agile methods brings change—for individuals, for the team, for the customer, and for the organization. Agile methods are foreign elements in most organizations where people and systems react in predictable, often dysfunctional ways. The challenge is to move from the old status quo to a new place in which most people feel comfortable and competent working in a new way. In this hands-on tutorial, Esther Derby discusses the four stages of change. Experience the feelings and responses at each stage and discover what you can do to help people climb the change curve. Practice three strategies for nurturing change: information, structure, and support. Find out what is really behind “resistance” to change and how you can learn from those resistance responses.
|
| Esther Derby is well known for her work in helping teams grow to new levels of productivity and coaching technical people who are making the transition to management. Focusing on interpersonal, group, and organizational dynamics, Esther co-authored Behind Closed Doors: Secrets of Great Management (with Johanna Rothman) and Agile Retrospectives: Making Good Teams Great (with Diana Larsen). Esther’s articles have appeared in Better Software magazine, Software Development, CrossTalk, and on-line at StickyMinds.com, CIO.com, scrumalliance.org, and ayeconference.com. |
|
 |
|
|
| |
| |
|
| Johanna Rothman, Rothman Consulting Group |
|
If you’re new to agile, you may not understand how agile projects work or your role in them. You may be puzzled by people self-assigning their work and by your new role as coach and facilitator rather than manager and supervisor. Without your familiar Gantt charts, you may not know how to answer management’s question—When will you be done?—when, in fact, agile projects provide the project manager more useful information than a plan-driven project. Yet, it is difficult for many project managers to make the transition to agile because they do not know what they can or should do. In this experiential tutorial, Johanna Rothman uses a small project to practice working on an agile project and teaches you to collect the data—both quantitative and qualitative—that tells you how the project and the team are progressing. Learn how to assess the project’s true state and understand what is needed to tell your management when you will be done.
|
| Johanna Rothman consults, speaks, and writes on managing high-technology product development. She assists managers, teams, and organizations to become more effective by applying her pragmatic approaches to the issues of project management, risk management, and people management. She’s helped engineering organizations, IT organizations, and startups hire technical people, manage projects, and release successful products faster. Johanna is the author of Manage It! Your Guide to Modern Pragmatic Project Management and Hiring the Best Knowledge Workers, Techies & Nerds: The Secrets and Science of Hiring Technical People, and coauthor of the pragmatic Behind Closed Doors, Secrets of Great Management. |
|
 |
|
|
| |
| |
|
| Scott Ambler, IBM Rational |
|
The Rational Unified Process (RUP) can be as agile as you want it to be. Although RUP is often mistakenly instantiated as a serial and documentation-heavy software process, many organizations choose instead to implement it in a lightweight and agile manner. After a quick review of the fundamentals of RUP and agile software development, Scott Ambler explores ways that many agile concepts were socialized by RUP in the 1990s and how “new” agile techniques easily can be tailored into RUP. Discover how RUP’s risk mitigation focus helps to scale agile techniques for large projects. In this interactive tutorial, discover that RUP done right is agile and that RUP done wrong is—just plain wrong.
|
|
Scott Ambler is the Practice Leader Agile Development in IBM’s Methods Group. He is the founder of the Agile Modeling, Agile Data, Agile Unified Process, and Enterprise Unified Process methodologies. Scott is the (co-)author of nineteen books, including Refactoring Databases, Agile Modeling, Agile Database Techniques, The Object Primer 3rd Edition, and The Enterprise Unified Process. Scott is a senior contributing editor with Dr. Dobb’s Journal. His personal home page is www.ibm.com/software/rational/bios/ambler.html.
|
|
 |
|
|
| |
|
|
| |
|
| Mike Cohn, Mountain Goat Software |
 |
Transitioning to an agile development process is unlike most transitions that organizations make. Transitions often begin when a strong, visionary leader plants a stake in the ground and says, “Let’s take our organization there.” Other transitions start when a team decides, “Who cares what management thinks, let’s do this.” In transitioning to agile, neither of these approaches is likely to lead to the long-term, sustainable change required. Mike Cohn explains the primary reasons why agile transitions fail and how to overcome them. Discover what is necessary for self-organizing teams to emerge and thrive and the role self-organization must play during the transition itself. Mike describes eight primary ways of getting, including Going All In, Start Small, and Impending Doom—and the advantages of each. Learn what approach will work best for you and what you must—and must not—do to succeed with agile.
|
| Mike Cohn is the founder of Mountain Goat Software, a process and project management consultancy and training firm. He is the author of Agile Estimating and Planning and User Stories Applied for Agile Software Development, as well as books on Java and C++ programming. With more than twenty years of experience, Mike has previously been a technology executive in companies of various sizes—from startup to Fortune 40. A frequent magazine contributor and conference speaker, Mike is a founding member of the Scrum Alliance and the Agile Alliance. He can be reached at [email protected]. |
|
|
|
|
| |
| |
|
| Rachel Davies, Agile Experience |
|
Find out what eXtreme Programming (XP) is all about, including a rich set of practices for developers to deliver solutions in short cycles of energized work. Rachel Davies delivers a guided tour of XP—how it works in practice along with tips on how to embed XP techniques within your team. Because XP runs counter to many traditional assumptions about how to develop software, Rachel uses interactive exercises to explore the practices of pair-programming, incremental design, and test-first development to provide an opportunity for you to experience them. Students won’t be cutting any code in the session so no laptops are required. Learn how XP helps developers understand and deliver what their customer needs and how to set the dials up to “10” on the code quality meter.
|
| Based in the UK with seven years of agile experience, Rachel Davies provides expert coaching to teams in agile software development techniques, including test-driven development, heartbeat retrospectives, and planning with user stories. She is passionate about agile software development because it increases the chance of successful projects in the face of complex problems. Director of the Agile Alliance, Rachel is internationally recognized in the agile community as a frequent presenter at industry conferences worldwide. You can contact Rachel at [email protected]. |
|
 |
|
|
| |
| |
|
| Wendy Friedlander & Oksana Udovitska, Oxygen Media |
|
Mock objects are an important component of test-driven development (TDD) because they simplify and decouple tests. So, why do many developers find this technique difficult to understand and employ? Wendy Friedlander and Oksana Udovitska demystify mock objects as they share their experiences in developing applications “test-first.” Learn why mocks are the key to truly understanding test-driven development. Wendy and Oksana define mock objects, explain their usage and benefits, and present several concepts including expectations, verification, constraints, and types. Learn about inversion of control, injection, and other object-oriented design principles. To make this session most productive and enjoyable, bring your problems, your questions, and your code.
|
| Wendy Friedlander has been using and advocating agile methodologies for many years. She has introduced companies to user stories, iterative planning, and test-driven development, and other agile practices. At Oxygen Media, she works on an agile team that embraces XP practices. Wendy is an expert in test-driven development, object-oriented design, and C#, including threading, remoting, Web services, WinForms, and WPF. She offers consulting and agile coaching through her company, Agile Solutions LLC. |
|
 |
| Currently a software developer with Oxygen Media, Oksana Udovitska spent five years programming in Java and Flash at the New York Stock Exchange where she helped create public-facing applications. At Oxygen, agile practices and pair programming have helped Oksana integrate her social nature with the demands of work. She made the transition from Java to C# and quickly became a strong and knowledgeable team member. Oksana believes the key to her lightning-fast transition is the agile methodology employed at Oxygen. |
|
 |
|
|
| |
| |
|
| Esther Derby, Esther Derby & Associates |
|
What makes agile teams agile? They inspect and adapt. Frequent feedback helps the team inspect and adapt the product. Retrospectives are a proven method used to inspect and adapt processes and methods. Esther Derby discusses how to design a retrospective using a flexible five-part framework that works for one-hour retrospectives, three-day retrospectives, and everything in between. This framework includes setting the stage, gathering data, generating insights, deciding what to do, and closing the retrospective. Esther examines what can go wrong when a team skips one of the stages of a retrospective. Working in small groups, you will design a retrospective and learn ways to keep retrospectives fresh and effective sprint after sprint.
|
| Esther Derby is well known for her work in helping teams grow to new levels of productivity and coaching technical people who are making the transition to management. Focusing on interpersonal, group, and organizational dynamics, Esther co-authored Behind Closed Doors: Secrets of Great Management (with Johanna Rothman) and Agile Retrospectives: Making Good Teams Great (with Diana Larsen). Esther’s articles have appeared in Better Software magazine, Software Development, CrossTalk, and on-line at StickyMinds.com, CIO.com, scrumalliance.org, and ayeconference.com. |
|
|
|
|
| |
| |
|
| Pollyanna Pixton, Accelinnova |
|
Leaders today are faced with an incredible challenge—delivering the right results to changing marketplaces, doing more with limited resources, improving processes to reduce costs, opening new markets, and keeping the company from falling into chaos. Amazingly though, the solutions to many challenges are already in your organization. How do you unleash the talent in your organization and foster the flow of ideas? In this hands-on and highly interactive tutorial, Pollyanna Pixton introduces you to the principles of collaboration and the tools you need to create collaborative cultures in your organization. Combining principles with practice, you will learn how to use the collaboration process to generate ideas and embrace change, identify barriers to innovation and agility, and discover and implement solutions. Practice with techniques and tools to become a more collaborative leader while learning the process for leading upwards and outwards.
|
| Pollyanna Pixton has implemented large scale agile projects including developing the Swiss Electronic Stock Exchange and control systems for electrical power plants throughout the world. She teaches Agile Project Management at the University of Utah and in organizations. Pollyanna has a Bachelors degree in mathematics, Masters degree in computer science, and graduate studies in theoretical physics. She co-founded the Agile Project Leadership Network (APLN) and chaired the Agile 2006 Leadership Summits in London and Minneapolis. Contact Pollyanna at [email protected]. |
|
 |
|
|
| |
| |
|
| Scott Ambler, IBM Rational |
|
One way to help scale agile methods for large, enterprise projects is to use a new approach to modeling software—Agile Model Driven Development (AMDD). In this interactive session Scott Ambler addresses some of the “less than pretty” aspects of agile software development as he describes how to take an AMDD approach to enhance and scale your agile software development efforts. Learn to model the complexities of large-scale software without getting bogged-down in mountains of paper work. Scott discusses ways to produce the minimum design documentation needed to communicate within and among teams. He explains how agile modeling fits into a test-driven development approach (TDD) for coding applications and how modeling, refactoring, and patterns can all work together to produce high quality software. If you are struggling with ways to become more agile on large, difficult projects or have contracted requirements for design documentation, the session is for you.
|
| Scott Ambler is the Practice Leader Agile Development in IBM’s Methods Group. He is the founder of the Agile Modeling, Agile Data, Agile Unified Process, and Enterprise Unified Process methodologies. Scott is the (co-)author of nineteen books, including Refactoring Databases, Agile Modeling, Agile Database Techniques, The Object Primer 3rd Edition, and The Enterprise Unified Process. Scott is a senior contributing editor with Dr. Dobb’s Journal. His personal home page is www.ibm.com/software/rational/bios/ambler.html |
|
|
|
|
| |
| |
|
| Ken Pugh, Net Objectives |
|
All projects, whether agile or traditional, need requirements. Ken Pugh explores the differences between agile and traditional requirements by interactively creating a set of agile-style requirements. These requirements are developed through progressive elaboration�rather than the big-bang, big-document approach. Ken first examines with you how stakeholders and requirements gatherers interact and communicate in an agile environment. Students will create a charter for a project that defines the overall scope and participate in a story-gathering workshop to create an initial set of stories. Learn when and how to revise stories by chunking and de-chunking to ensure that the requirements fulfill the characteristics of good stories. Explore user roles, personas, and narratives to determine additional stories. Practice prioritizing the requirements and estimating their business value to help in that prioritization. At the end of the session students will begin constructing use cases and acceptance tests to add details to the requirements.
|
| Ken Pugh (ken.pugh@netobjectives) is a Fellow Consultant for Net Objectives. He has over one-third of a century of experience in software development, from gathering requirements for stock market analysis to testing real-time radar systems. He consults, trains, and mentors on agile processes and technology topics ranging from Object-Oriented Design to Test-Driven Development. He has written several programming books, including �Interface-Oriented Design� and the 2006 Jolt Award winner �Prefactoring�. He has spoken numerous times at software development conferences over the past twenty years. He has provided expert testimony in both civil and criminal cases. When not computing, he enjoys snowboarding, windsurfing, biking, and hiking the Appalachian Trail. |
|
 |
|
|
|
Top of Page
|
|
