development

Conference Presentations

It’s Agile, Not Fragile
Video

The time is now to rethink the way you and your teams build, test and deliver applications. In this session, we will share the insights, best practices and software innovation to address the challenge of rapid delivery of today’s user-centric applications. 
Kelly Emo and Michael Cooper, HP
Android Mobile Development: A Test-driven Approach

Few topics are hotter these days than mobile software development. It seems that every company is rushing to release its own mobile application. However, when it comes time to build that software, companies quickly discover that things are different now.
Jeff "Cheezy" Morgan, LeanDog
STARCANADA 2013 Keynote: Cool! Testing's Getting Fun Again
Video

The last exciting era in testing was the late ‘90s when the web turned technology on its ear, the agile movement overthrew our processes, and the rise of open source gave us accessible and innovative tools. However, since then, Jonathan Kohl finds it has been a lot of the same-old, same-old.
Jonathan Kohl, Kohl Concepts, Inc.
STARCANADA 2013 Keynote: Lighting Strikes the Keynotes
Video

Lightning Talks are a popular part of the STAR conferences. Lightning Talks consists of a series of five-minute talks by different speakers within one presentation period and are an opportunity for speakers to deliver their single biggest bang-for-the-buck idea in a rapid-fire presentation.
Lee Copeland, Software Quality Engineering
STARCANADA 2013: Concurrent Testing Games: Developers and Testers Working Together

The best software development teams find ways for programmers and testers to work closely together. These teams recognize that programmers and testers each bring their own unique strengths and perspectives to the project. However, working in agile teams requires us to unlearn...
Nate Oster, CodeSquads LLC
Estimating in Software Development: No Silver Bullets Allowed
Slideshow

What do poker, Greek oracles, an Italian mathematician from the Middle Ages, and the path of hurricanes have in common? Given the title of this presentation, chances are it has something to do with estimation, and you'll have to attend this session to get the full connection. Kent McDonald explores the challenges and realities of trying to estimate software-related knowledge work-analysis, testing, development, and the entire project effort. A major challenge is that there are no guaranteed ways to arrive at perfectly accurate estimates, which not surprisingly is why they are called estimates. Kent introduces and gives you a chance to practice quick and practical estimating techniques that will work in different situations-guesstimating, break it down and add it up, and planning poker.
Kent McDonald, Knowledge Bridge Partners
Massive Continuous Integration and Light-speed Iterations
Slideshow

Continuous integration (CI) has become a buzzword, with most engineering organizations claiming they've adopted the practice. However, the sad truth is that unreliable tests, long feedback loops, and poor configuration management block their efforts and minimize CI's potential benefits. Jesse Dowdle shares how AtTask radically redesigned its engineering pipeline and, through massive CI scaling, drove three days of testing to just minutes. Learn the pros and cons of different CI systems and how to integrate them with the cloud. Watch a live demo of AtTask's internal test and CI systems, which they’ve designed to make "Every commit a potential release candidate"-meaning that every commit is an iteration. Arm yourself with the talking points to sell massive CI to executives.
Jesse Dowdle, AtTask, Inc.
Creating Great User Experiences: Tips and Techniques
Slideshow

Many software people look at creating great user experiences as a black art, something to guess at and hope for the best. It doesn't have to be that way! Jennifer Fraser explores the key ingredients for great user experience (UX) designs and shares the techniques she employs early-and often-during development. Find out how Jennifer fosters communications with users and devs, and works pro-actively to ensure true collaboration among UX designers and the rest of the team. Whether your team employs a formal agile methodology or not, Jennifer asserts that you need an iterative and incremental approach for creating great UX experiences. She shares her toolkit of communication techniques-blue-sky brainstorming sessions, structured conversation, and more-to use with different personality types and describes which types may approach decisions objectively versus empathetically.
Jennifer Fraser, Macadamian
Back to the Basics: Principles for Constructing Quality Software
Slideshow

Using an analogy to the building codes followed by architects and contractors in the construction of buildings, Rick Spiewak explores the fundamental principles for developing and delivering high quality, mission-critical systems. Just as buildings are constructed using different materials and techniques, we use a variety of languages, methodologies, and tools to develop software. Although there is no formal "building code" for software, software projects should consider-and judiciously apply-the recognized "best" practices of static analysis, automated unit testing, code re-use, and peer reviews. Rick takes you on a deep dive into each of these techniques where you'll learn about their advantages, disadvantages, costs, challenges, and more.
Rick Spiewak, The MITRE Corporation
The Right Question for the Right Requirements
Slideshow

How often have you gone down the road of developing software almost to completion only to discover new requirements that require significant design and coding changes at the last minute? Requirements analysis is not just writing down what customers say they want. It's about digging down and discovering what they need. Without real analysis, our requirements often end up as poorly defined lists, anemic mock-ups, and incomplete or inconsistent models. Jack Jones spotlights one simple technique to discover these needs: Ask "why?" When the customer states a requirement, ask "why?" to delve down a level to discover their real problem, need, or opportunity. You may find you need to repeat "why?" a number of times. Join Jack to explore the very real consequences of not comprehending customer needs early in the process, and practice better communications techniques to avoid unnecessary requirements and scope changes.
Jack Jones, KMI

Pages

CMCrossroads is a TechWell community.

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