Extreme Programming is one of the early agile mindset based approach "software engineering specific practice" that was developed in 1996 by Kent Beck for Chrysler Payroll System development. The concepts of Extreme Programming are so popular; we utilize them in almost all Team Level, System & Enterprise Scaling approach as the foundations.
Extreme Programming is pushing all the traditional/ordinary and slow programming approaches, communication & collaboration, planning, integration, deploying to extreme levels for high productivity, close collaboration and communication, high value for customers and business and at the same programmer's welfare by following simple value & principles based practices.
Extreme or Xtreme programming is also considered to be a flexible, light-weight, fun and at the same time highly focused on business value, welfare and mutual benefit of the employees and customers.
History of XP
Xtreme programming stated as a restructuring programme of C3 Payroll system in 1996. Since then, It has created a broad and deep impact in the agile community and also scaling agile practices at the organization or enterprise scale. Most of the building blocks and foundations of modern IT high-quality software engineering practices are from the Xtreme programming practices.
The Goal of XP is excellent software development.
It is also from my observations and experience, "Lean is Agile for the manufacturing industry, while Agile is Lean for the software industry.
XP has an agile mindset - based on values & principles - ways-of-working.
XP suggests that the Principle is the bridge and bridges the gaps between Practices and Values. The Principles also can be domain specific.
XP believes in sustainable pace and suggests 40hr per week work schedule for individuals. Promotes Pair programming for knowledge sharing and shared understanding.
XP has activities, values, principles and practices.
Coding, Testing, Listening and Designing.
Communication, Simplicity, Feedback, Courage, and Respect.
Humanity, Economics, Mutual-Benefit, Self-Similarity, Improvement, Diversity, Reflection, Flow, Opportunity, Redundancy, Failure, Quality, Baby Steps, Accepted Responsibility
XP Practices (Primary)
Sit Together, Whole Team, Informative Workspace, Energized work, Pair Programming, Stories, Weekly-Cycle, Quarterly-Cycle, Slack, Ten-minute Build, Continuous Integration, Test-First Programming, Incremental Design
XP Practices (Corollary)
Real Customer Development, Increment Deployment, Team Continuity, Shrinking Teams, Root-Cause Analysis, Shared Code, Code and Tests, Single code base, Daily Deployment, Negotiated Scope Contract, Pay-Per-Use
XP for High-Quality Software Development
XP Practices promote that the entire team works together in the same office.
XP Practices promote that the Whole Team approach (all required skills Multi-discipline, functional approach to delivering value).
XP Practices promote information radiator type of approach, where Product, Teams progress is visible and updated.
XP Practices promote that people achieve their work at a sustainable pace, and avoid working overtime, during sickness.
XP Practices promote Pair work, where driver-navigator role. This concept has evolved into many other modern practices.
XP Sample/Actual card using User Story Format.
XP Promotes "Stories" format with Acceptance Criteria, which many agile practices are now adopting.
XP promotes small Releases through continuous integration and other extreme programming practices. Small Releases helps to deliver a small working increment (User Story) in a weeks time. Development Team can do a weekly review.
XP promotes the quick build, capacity based planning, Test-first programming, an incremental design that helps to support emergent design.
XP is one of the early agile practice which promotes a mindset based on values, principles, and practices. The practices are both technical and for the growth of the people (or programmer's welfare).
XP practices, Scrum Framework, and Kanban can be considered to complement each other. Kanban promotes flow processes, XP Promotes good engineering practices while Scrum promotes a framework approach.
XP Promotes feedback approach and the high-speed collaboration, communication, and feedback of the working software.
Scrum, XP, Kanban, and DevOps considered to be the foundation and also enabling the concept of the Continuous Delivery pipeline.
Temenos Effect Gathering 2018- Bengaluru, India(Dec 29, 2018)
An event dedicated to the idea of personal mastery, for nurturing your beautiful self, for change agents and leaders to become their true selves.
For more details, visit our website: https://www.visiontemenos.com/events