Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Manoel Pimentel , translated by Felipe Rodrigues on Nov 17, 2008
Last week was hot in international scenario on software development. The SEI (Software Engineering Institute) recently published a report entitled " CMMI or Agile: Why Not Embrace Both!", which addresses the integration between the ideas and practices of the CMMI with the ideas and practices of Agile as something possible in software development projects.
According to the document, which counted on participation of some famous agilists as David Anderson, the focus of this initiative is:
More dialogue would be healthy and beneficial for users, the paradigms, and the broader community.
Also in another sentence of the document, which is explained the desired result of that:
We hope this report encourages both CMMI and Agile proponents (ideally, everyone in software related industries) to do the following:
- Recognize the value of each paradigm.
- Resist common misperceptions.
- Continue experimenting, learning, and reporting on what works and in which contexts.
The document also addresses other issues such as:
In general, different reactions have occurred by the agile community, especially in Brazil (see messages in portuguese here Visão Ágil and here Scrum-Brazil, where many feel that this is pure opportunism, because they can’t see the synergy between these two worlds. And others see this as a good opportunity for all and a great chance to fix some problems from the past, on the understanding and adoption of Agile and CMMI itself.
But in truth, this was only the first step towards a clearer synergy between Agile and CMMI and perhaps there are still many questions that only with continuous experimentation and adjustment, we could really know whether this relationship is possible and more important if it is healthy.
Case Study: IBM's Agile Transformation
A Guide to Branching and Merging Patterns
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
No comments
Watch Thread Reply