About the Talk
January 30, 2011 7:30 AM
Cal State FullertonCal State Fullerton
Better communication through code; Creating a shared language for your team
An experimental Agile Toolkit.
Software development, by its nature, is a series of translations and compromises. What the end user wants, what the customer is willing to pay for, and what is technically feasible rarely combine to form a unified set of features. A deeper understanding between technical and non-technical people is needed, in particular at the communication divide between stakeholders and developers.
In this talk the dynamic duo, Alline Watkins and June Clarke will show you how to develop a domain-specific, ubiquitous language, how to lessen the responsibility gap between managers and developers and how to use your code base as the central source for your requirements and documentation, to improve communication for the whole team.
Does your source code lack knowledge? Is it a complex mess that just doesn't make any sense to anyone, even possibly you? If you or one of your employees left work now, would others be able to make sense of it?
Source Agile is a system that capture and display document information about your software, dynamically from your source code. A new tool for your project, shedding light on the darkness of codebase by extracting a smart, easy to read summary of the content.
Just write your code well and let Source Agile take care of the rest.
Process/Mechanics: The presentation will begin with a 10-minute tutorial on how to use a ubiquitous language on your team. The benefits of this language will closely align your requirements with the source code.
Using this as a basis, we will demonstrate our web tool to show the features that enable stakeholders to better understand what is going on technically on the project, and how to use the code base as a place to store requirements, priorities and metrics.
By fleshing out the concept of using a team-wide ubiquitous language, we have developed a simple web application that opens your codebase to stakeholders. Non-technical people can view and understand the high-level structure of the code, and contribute new requirements in a context-sensitive way. Requirements and documentation are integrated with the source code making your codebase a central location for most of your project artifacts. Project status and end-user documentation can then be dynamically extracted from your source code.
Learning outcomes: - New ideas for producing documentation for an Agile project at a low cost. - An understanding of the concept that a code repository can also be used to centralize requirements, end-user documentation and planning information. - How to develop and apply ubiquitous language in your team. - How to collaborate programmers and non-programmers.