Entity

Time filter

Source Type

Porto Alegre, Brazil

Blunden C.,ThoughtWorks | Blunden C.,Thoughtworks Inc.
Lecture Notes in Business Information Processing | Year: 2010

Stuck in the purgatory of an immature "Agile" IT department and old world project management office, facing up to eighteen month lead times on analysis and sign off, off shoring contractors and people new to Agile. These are the experiences of how we created a bubble of effectiveness through applying systems thinking and radical changes in delivery process. The result was a clear success with practically zero defects and a model of future development within the company. © 2010 Springer-Verlag. Source


Ramesh A.,MSRIT | Srinivasa K.G.,MSRIT | Pramod N.,ThoughtWorks
5th International Conference on the Applications of Digital Information and Web Technologies, ICADIWT 2014 | Year: 2014

We introduce a graph and an intersection based technique which uses statistical and semantic analysis for computing relative importance of textual units in large data sets in order to summarize text. Current implementations consider only the mathematical/statistical approach to summarize text. (like frequency, TFIDF, etc.) But there are many cases where two completely different textual units might be semantically related. We hope to overcome this problem by exploiting the resources of WordNet and by the use of semantic graphs which represents the semantic dissimilarity between any pair of sentences. Ranking is usually performed on statistical information. The algorithm constructs semantic graphs using implicit links which are based on the semantic relatedness between text nodes and consequently ranks nodes using a ranking algorithm. © 2014 IEEE. Source


Webber J.,ThoughtWorks
Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) | Year: 2010

The Web has emerged as a viable platform for building distributed systems beyond its traditional scope as a scalable means of sharing and disseminating information. In this paper I present observations from recent industrial development projects where commodity Web infrastructure and common patterns have been used to create large, scalable, and dependable computer systems. © 2010 Springer-Verlag Berlin Heidelberg. Source


Middleton P.,Queens University of Belfast | Joyce D.,ThoughtWorks
IEEE Transactions on Engineering Management | Year: 2012

This case study examines how the lean ideas behind the Toyota production system can be applied to software project management. It is a detailed investigation of the performance of a nine-person software development team employed by BBCWorldwide based in London. The data collected in 2009 involved direct observations of the development team, the kanban boards, the daily stand-up meetings, semistructured interviews with a wide variety of staff, and statistical analysis. The evidence shows that over the 12-month period, lead time to deliver software improved by 37%, consistency of delivery rose by 47%, and defects reported by customers fell 24%. The significance of this work is showing that the use of lean methods including visual management, team-based problem solving, smaller batch sizes, and statistical process control can improve software development. It also summarizes key differences between agile and lean approaches to software development. The conclusion is that the performance of the software development team was improved by adopting a lean approach. The faster delivery with a focus on creating the highest value to the customer also reduced both technical and market risks. The drawbacks are that it may not fit well with existing corporate standards. © 2006 IEEE. Source


Wampler D.,DRW Holdings | Clark T.,Middlesex University | Ford N.,ThoughtWorks | Goetz B.,Oracle Inc.
IEEE Software | Year: 2010

The guest editors discussed the pragmatics of multiparadigm programming with Neal Ford and Brian Goetz. Should the average team adopt MPP? Can it do so successfully? Neal argues that such teams can't afford not to adopt MPP, if they want to stay competitive. However, the risks can be mitigated by careful adoption, based on demonstrable value, with appropriate division of responsibilities among team members, based on their skills. Brian argues that developers often make poor choices, driven more by personal interests than by concern for what is ultimately best for team success. Neal offers some real-world examples of how Thoughtworks has used MPP effectively. © 2010 IEEE. Source

Discover hidden collaborations