Abstract: Software "best" practices depend  entirely on context ­ in terms of the problem domain, the system constructed, the software designers, and the  "customers" ultimately deriving value from  the system. Agile practices no longer  have the luxury of "choosing" small
non-mission   critical  projects with collocated  teams. Project stakeholders  are selecting and adapting practices based on a combination of interest, need and staffing. For example, growing product portfolios through a merger or the acquisition of a company exposes legacy  systems to new staff, new software integration challenges, and new ideas. Innovation in communications (tools and processes) to span the growth and contraction of both information and organizations, while managing the adoption of changing software practices, is imperative for success.

CV: with responsibilities for developing and managing university research relations. Previously, Steve held a variety of tech transfer roles at Qualcomm (San Diego), BNR/Nortel (Ottawa, Santa Clara), and the Software Engineering Institute (SEI) at Carnegie Mellon University (Pittsburgh) focused on software best practices including tools, methods, training and software reuse strategies. Steve holds doctorate (Electrical Engineering) and bachelors (Physics and Computer Science) degrees from McGill University in Montréal, Canada and a masters degree in Physics from Queen's University at Kingston, Canada. He has published over 50 papers/panels/workshops and is a member of the ACM and a senior member of the IEEE.

Homepage Cisco Research