Tags / 2010

Tagged with “2010” (124) activity chart

  1. Facilitation Foundations: Eliminating Waste From Agile

    Everyone has been to an Agile meeting that has little or no value and that’s felt like a complete waste of time. Facilitation Foundations is designed to offer attendees a chance to learn more about how to make meetings more valuable and save everyone time and money. This talk focuses on what makes meetings work and identifies negative experiences we all encounter when it comes time to attend or facilitate these common meetings. What should we be doing? What should we be avoiding? What could we do to improve the way we facilitate and or attend meetings? How can we make them more effective?

    —Huffduffed by olafursverrir one year ago

  2. Discount Usability Testing for Agile Teams

    Agile methods promise an iterative and incremental approach to building software. Unfortunately, the iterative portion is often omitted when it comes to incorporating true user feedback and observation. In this workshop, participants will learn how to apply a method known as “discount usability testing” to allow for fast and useful feedback from users that can be incorporated into their product delivery process.

    —Huffduffed by olafursverrir one year ago

  3. Systems Thinking and the Learning Organization

    Great software is only possible in a true Learning Organization. This talk gives a pragmatic exploration of the connections between Senge’s five disciplines for learning organizations and the Agile software development framework. Specifically making use of Senge’s three legged stool of Aspiration, Understanding Complexity, and Reflective Conversation, Agile provides a strong pattern for creating and changing the realities of business and customer value delivery.

    —Huffduffed by olafursverrir one year ago

  4. Growing Up Agile

    In 2000, Agile was revolutionary. In 2010, Agile is stagnant. There are two Agile worlds today: The first is pushing the same practices and processes they’ve been pushing for the last decade. The second takes many of these practices and processes for granted. Sadly, there’s little interaction between the two. In this discussion, we’ll look at the rift between the two communities, how to bridge it, and the exciting possibilities that can exist when we do.

    —Huffduffed by olafursverrir one year ago

  5. A Tale of Two Cities - Early Adoption Stories

    This experience report is about early adoption issues within two companies which share certain similarities (large, very distributed) but have differences as well (services vs products, IT vs engineering focus, close vs distant customers).

    —Huffduffed by olafursverrir one year ago

  6. Agile Development with Interns

    The intern program at inContact uses 5-10 interns every quarter for a period of 10 weeks, and has been running for 1 1/2 years. Some of the challenges with using interns are discussed:

    —Huffduffed by olafursverrir one year ago

  7. Test Driven Design - Coupling Loosely

    Mock objects are a good way to break apart a legacy system to test it. However, they do not improve coupling (few dependencies between units) or cohesion (each unit does one thing). Making code easy to change requires using indirections with looser coupling. In this information-dense, code-oriented session, we’ll learn key indirections and their impacts on your design. Next time, choose the right indirection for the job rather than just reaching for another mock object.

    —Huffduffed by olafursverrir one year ago

  8. The View from Here: Reconciling User Experience, Product Management and Agile Development

    Agile strives for good communication with their customers. The Embedded User Experience works with the customer to understand what they need, when even the customer may not understand themselves. We teach how to paper prototype and how to do on-site and remote usability testing. Come to this workshop to learn rapid prototyping techniques, Usability Testing (Remote and On-site), Cultural and Physical Modeling, Heuristic Evaluations and much more.

    —Huffduffed by olafursverrir one year ago

  9. Creating Big Picture Designs Without Big Design

    One of the toughest problems facing agile UX designers is keeping the big picture in mind while designing incrementally. This talk builds on prior work at Alias (now Autodesk) that described successful agile adaptations of usability testing, contextual inquiry and iterative prototyping. I’ll present a framework we used to create and implement multi-sprint designs for a complex product without violating the agile taboo against big design.

    —Huffduffed by olafursverrir one year ago

  10. What We Learned in 8829 Hours of Pair Programming

    Eight thousand eight hundred and twenty-nine hours of pair programming – does that make us experts yet? No, but we sure have learned a few things in five plus years. Many agile programmers see pair programming as too hard, but don’t have the advantage of pairing all the time. Without applying pairing consistently, team members will not gain trust quickly. Without trust, pairing is difficult. This session will examine how practice makes perfect when it comes to being a good pair partner.

    —Huffduffed by olafursverrir one year ago

Page 2 of 13