Conference Presentations

Agile Dev, Better Software & DevOps Conference West 2015: Emergent Design: History, Concepts, and Principles
Slideshow

Software design is about change. A good design facilitates adding features—and adding new developers to the team. Yet any change to the code impacts design and can damage existing functionality. Without design idioms and practices, the code can degrade into a maintenance nightmare...
Rob Myers, Agile Institute
Agile Development Conference & Better Software Conference East 2014: Emergent Design: History, Concepts, and Principles
Slideshow

Software design is about change. A good design facilitates adding features—and adding new developers to the team. Yet any change to the code impacts design and could damage existing functionality. Without design idioms and practices, the code can degrade into a "big ball of spaghetti”...
Rob Myers, Agile Institute
Avoiding Over Design and Under Design
Slideshow

The question of how much design to do up-front on a project is an engaging conundrum. Too much design often results in excess complexity and wasted effort. Too little design results in a poor architecture or insufficient system structures which require expensive rework and hurt more in the...
Al Shalloway, Net Objectives
Non-Functional Requirements: Forgotten, Neglected, and Misunderstood
Slideshow

Implementing non-functional requirements is essential to build the right product. Yet teams often struggle with when and how to discover, specify, and test these requirements. Many teams neglect non-functional requirements up front, considering them less important or unrelated to user...
Paul Reed, EBG Consulting
Making Testing at eBay More Realistic
Slideshow

Have you had customers report issues that cannot be reproduced in the test environment? Have you had defects leak into production because your test environment is not...
Kamini Dandapani, eBay, Inc.
Agile Development Conference & Better Software Conference East 2013: Avoiding Overdesign and Underdesign
Slideshow

The question of how much design to do up-front on a project is an engaging one.  Too much design often results in overkill, complexity, and wasted effort. Too little design results in insufficient system structures that require later rework, additional complexity, and wasted effort.
Ken Pugh, Net Objectives
Keynote: Know the Way, Show the Way, Go the Way: Scaling Agile Development
Video

Tired of the claims that Scrum, XP, and kanban don’t scale beyond a few teams? Overwhelmed by management’s resistance to the organizational changes needed to really follow agile principles? Concerned with the lack of proven practices required to scale agile methods to the next level?
Dean Leffingwell, Leffingwell LLC
Behavior-Driven Design in Practice
Slideshow

One of software development’s  greatest challenges is combining business needs with technical abilities to build products that customers want. Many development methodologies attempt to achieve this, but Nir Szilagyi and Janarthanan Eindhal think that few connect the dots as well as...
Nir Szilagyi, eBay, Inc. & Janarthanan Eindhal, eBay, Inc.
A UX Strategy for Persona Research
Slideshow

Research into your users’ personas can provide deep insights into their needs and validate your product design. This research doesn’t have to take months; it can often be done in two weeks, during sprint 0. Unfortunately, many companies using agile methods don’t invest in personas and a...
Nellie LeMonier, Perforce Software, Inc.
Right-sized Architecture: Integrity for Emerging Designs
Slideshow

In agile projects, design ideally "emerges" over the course of development. However, if teams primarily focus on independent user stories, they risk losing sight of the product's vision and the integrity of well-thought-out architecture. Ken Kubo shares techniques he's used to improve the chances that a product's design will emerge into a cohesive and coherent architecture that serves its customers for many years. Join Ken to find out how you can incorporate contextual design principles and simple, visual techniques as part of his "A-Little-Before-Its-Time Design" framework. You can add these practices into your agile workflow to maintain a shared team understanding of your product's vision and the system's emerging design. Ken believes that you can only realize all the promises of agile development with a clearly and constantly communicated product vision and a set of architecture goals.
Ken Kubo, Northrop Grumman Corporation

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.