If you don't know where you are, a map won't help., Watts Humphrey.

Bill Nichols

This statement describes the frustrating situation in which you know where you would like to go, but you don't know how to navigate a course to get there. This is the circumstance many individuals, teams, projects, and organizations face; they know they need better quality but don't know how to achieve it. One popular but naïve approach is to choose some practices and techniques and hope they lead you to the needed performance improvement. Fortunately, there is a much better way. This tutorial will describe how the Team Software Process (TSP) can dramatically improve your software quality capabilities with comprehensive, data driven, and proven methodology. The first step in addressing quality is to understand that it is not a destination or a final state, but an incremental set of capabilities and stages of development. Each individual, team, and project within an organization can be operating at different stages along the path to producing high-value, high-quality products and services. By focusing on identifying capabilities and quality levels and understanding the associated root cause issues, one can select the most effective direction to take to achieve the next stage and avoid costly dead-ends and wrong turns. This tutorial will take a deeper look into the eight stages of development in the quality journey using TSP. The presenters will describe each stage, identify their differences, and discuss techniques used to improve software quality. This tutorial goes beyond a theoretical presentation; the tools and techniques presented have been rigorously field tested and validated. Data and experience will be shared from organizations who use TSP and are benefitting from these concepts.

Bill Nichols

Bill Nichols joined the Software Engineering Institute (SEI) in 2006 as a senior member of the technical staff and serves as a PSP instructor and TSP coach with the Team Software Process (TSP) Program. Prior to joining the SEI, Nichols lead a software development team at the Bettis Laboratory near Pittsburgh, PA, where he had been developing and maintaining nuclear engineering and scientific software for 14 years. His publications include the interaction patterns on software development teams, design and performance of a physics data acquisition system, analysis and results from a particle physics experiment, and algorithm development for use in neutron diffusion programs. He has a doctorate in physics from Carnegie Mellon University.




Technical Debt: At the Intersection of Decades of Empirical Software Engineering Research

Carolyn Seaman

The term "technical debt" refers to the relationship between the short-term benefits of delaying certain software maintenance tasks and the long-term cost of those delays. This metaphor frames the problem of delayed maintenance tasks as a type of "debt," which brings a short-term benefit (usually in terms of higher productivity or shorter release time) but which might have to be paid back, with "interest," later. The "principal" on the debt is the amount of effort required to "pay off" the debt (i.e. complete the task), while the "interest" is the potential penalty (in terms of increased effort and decreased productivity) that will have to be paid in the future as a result of not completing these tasks in the present. While technical debt is only a metaphor, it describes a very real phenomenon that is well understood by practitioners. The phenomenon is not new, but the metaphor provides new ways of talking about it and inspires new potential solutions that could be adapted from the finance domain. For empirical researchers, it also provides the ultimate practical application of several long-term streams of work, including software quality, software metrics, risk management, maintenance, and program analysis. This provides a new opportunity to couch research results in these areas in terms that practitioners find interesting and useful, thus allowing a new avenue for technology transfer.

Carolyn SeamanDr. Carolyn Seaman is an Associate Professor of Information Systems at the University of Maryland Baltimore County (UMBC). Her research generally falls under the umbrella of empirical studies of software engineering, with particular emphases on maintenance, organizational structure,communication, measurement, COTS-based development, and qualitative research methods.Dr. Seaman is also a Research Fellow at the Fraunhofer Center for Experimental Software Engineering, Maryland, where she participates in research on experience management in software engineering organizations and software metrics. Currently, during the 2012-13 academic year, she is spending a sabbatical as a visiting researcher in Brazil, based at the Center for Informatics at the Federal University of Pernambuco in Recife, Brazil, where she is conducting research in the management of software technical debt. She holds a PhD in Computer Science from the University of Maryland, College Park, a MS in Information and Computer Science from Georgia Tech, and a BA in Computer Science and Mathematics from the College of Wooster (Ohio). She has worked in the software industry as a software engineer and consultant, and has conducted most of her research in industrial and governmental settings (e.g. IBM Canada Ltd., NASA, Xerox).



The Fast & the Furious: The Software Drift.

Eduardo Mangarelli y Fernando Machado

In the latest years software is dealing and coping with more and more challenges than ever before. Today's software applications are expected to manage massive amounts of data from multiple unstructured sources; run as services; be able to support large number of concurrent users; scale up to unforeseeable limits; provide always-on, high availability features while supporting undependable hardware; support mobile users and multiple devices’ form different vendors (among other sources of complexity). These expectations are disrupting the way we used to engineer software systems. How are we dealing with them?

Carolyn Seaman

Eduardo Mangarelli is the Director of Technology for the Developers & Platform Team at Microsoft Latin-American. He has a System Engineer Degree from the Universidad ORT Uruguay. Mangarelli also works with different organizations and communities, like Endeavor and Fondo Emprender, to foster the Startups´ ecosystems and mentoring local companies. On the academic space, Mangarelli is a professor at the ORT University, teaching different matters around technology, software design and innovation. He is also speaker at different Industry conferences around topics like Digital Marketing, Innovation and Technology.

Carolyn Seaman

Fernando Machado is an Enterprise Consultant and Professor in Information and Communication Technologies. He received is PhD in Computer Science from University of Alcalá in Madrid, Spain, in 2006. In 1996 he received his Information Technology degree from Universidad Católica in Montevideo, Uruguay. Fernando is now a part-time Professor in Universidad Católica, where he teaches Programming and Software Engineering.In the industry, he is currently working as Enterprise Architect at Microsoft, since 2010. Before joining Microsoft, Fernando was a free-lance consultant, since 2005. In 2008 he was nominated Microsoft Most Valuable Professional. Previously, he worked during 10 years as Software Architect and Developer for regionals Independent Software Vendors, building Enterprise Resource Planning application software packages for M&SB.










Doctoral SymposiumDoctoral Symposium

Industrial forumIndustrial forum



Universidad ORT Uruguay Universidad de la República antel

Media Partner:

El País


GeneXus consulting One Tree Microsoft El sitio de los clasificados
Tata Consultancy Services Mercado libre Globant Tilsor Instituto uruguayo de normas técnicas PLOP


Centro Latinoamericano de Estudios en Informática Agencia Nacional de Investigación e Innovación IEEE computer society Cámara uruguaya de tecnologías en la información