spine.wiki
Values
http://spine.wiki/values.html
A free Spine Model catalog to which anyone can contribute. Generic List of Values. Values of Extreme Programming. Blog comments powered by Disqus. Generic List of Values. Values of Extreme Programming. Is licensed under a Creative Commons Attribution 4.0 International License.
spine.wiki
Design Improvement (Refactoring)
http://spine.wiki/practice/Refactoring
A free Spine Model catalog to which anyone can contribute. Last updated 22 November 2015 by Kevin Trethewey. Extreme Programming focuses on delivering business value in every iteration. To accomplish this over the course of the whole project, the software must be well-designed. The alternative would be to slow down and ultimately get stuck. So XP uses a process of continuous design improvement called. From the title of Martin Fowler’s book, Refactoring: Improving the Design of Existing Code. Are a critic...
spine.wiki
Small Releases
http://spine.wiki/practice/SmallReleases
A free Spine Model catalog to which anyone can contribute. Last updated 22 November 2015 by Kevin Trethewey. XP teams practice small releases in two important ways:. Second, XP teams release to their end users frequently as well. XP Web projects release as often as daily, in house projects monthly or more frequently. Even shrink-wrapped products are shipped as often as quarterly. For more information, review the XP archetype. Blog comments powered by Disqus. First, the team releases running, tested softw...
spine.wiki
Whole Team
http://spine.wiki/practice/WholeTeam
A free Spine Model catalog to which anyone can contribute. Last updated 22 November 2015 by Kevin Trethewey. All the contributors to an XP project sit together, members of one team. None of these roles is necessarily the exclusive property of just one individual: Everyone on an XP team contributes in any way that they can. The best teams have no specialists, only general contributors with special skills. For more information, review the XP archetype. Blog comments powered by Disqus.
spine.wiki
Practices
http://spine.wiki/practices.html
A free Spine Model catalog to which anyone can contribute. Practices of Extreme Programming. Blog comments powered by Disqus. Practices of Extreme Programming. Is licensed under a Creative Commons Attribution 4.0 International License.
spine.wiki
Tools
http://spine.wiki/tools.html
A free Spine Model catalog to which anyone can contribute. Tools for Visualising Work In Progress. Blog comments powered by Disqus. Tools for Visualising Work In Progress. Is licensed under a Creative Commons Attribution 4.0 International License.
spine.wiki
Test Driven Development
http://spine.wiki/practice/TDD
A free Spine Model catalog to which anyone can contribute. Last updated 22 November 2015 by Kevin Trethewey. It isn’t enough to write tests: you have to run them. Here, too, Extreme Programming is extreme. These programmer tests , or unit tests are all collected together, and every time any programmer releases any code to the repository (and pairs typically release twice a day or more), every single one of the programmer tests must run correctly. One hundred percent, all the time!
spine.wiki
Practices of Extreme Programming
http://spine.wiki/practice/PracticesOfXP
A free Spine Model catalog to which anyone can contribute. Practices of Extreme Programming. Last updated 22 November 2015 by Kevin Trethewey. XP’s philosophy on Practices. Is very non-prescriptive, and advises an explorative approach, based on the XP Principles. Practices recommended by Kent Beck. Practices as presented in eXtreme Programming Explained, 2nd Edition by Kent Beck. The second of the Three Extremos. Practices recommended by Ron Jeffries. Is the third of the Three Extremos.
spine.wiki
Tags
http://spine.wiki/tags.html
A free Spine Model catalog to which anyone can contribute. Visualize and limit WIP, reduce batch sizes, and manage queue lengths. Take an Economic View. Assume Variability; Preserve Options. Apply cadence, synchronize with cross-domain planning. Capacity of a work system. Resource vs Flow Optimisation. Responding to change over following a plan. Customer collaboration over contract negotiation. Working software over comprehensive documentation. Individuals and interactions over processes and tools. Build...
SOCIAL ENGAGEMENT