A healthy environment of openness and honest feedback among team members is critical for a team to learn and adapt quickly in order to perform at their best potential.
Minimize the scope of your tasks
Try to minimize the scope of your working tickets to the minimum value that could make sense, in term of deployability.
Keeping in mind a small and concrete goal to achieve by the given ticket description helps you to focus on the Acceptance Criteria that the tickets ask you to complete.
There is an excellent kata/exercise to train exactly this, it’s called “Elephant Carpaccio”.
Agile software development values
- Individuals and Interactions over processes and tools
- Working Software over comprehensive documentation
- Customer Collaboration over contract negotiation
- Responding to Change over following a plan
Agile software development principles
- Customer satisfaction by early and continuous delivery of valuable software.
- Welcome changing requirements, even in late development.
- Deliver working software frequently (weeks rather than months)
- Close, daily cooperation between business people and developers
- Projects are built around motivated individuals, who should be trusted
- Face-to-face conversation is the best form of communication (co-location)
- Working software is the primary measure of progress
- Sustainable development, able to maintain a constant pace
- Continuous attention to technical excellence and good design
- Simplicity—the art of maximizing the amount of work not done—is essential
- The best architectures, requirements, and designs emerge from self-organizing teams
- Regularly, the team reflects on how to become more effective, and adjusts accordingly
Extreme Programming Values
Extreme Programming (XP) is based on values. The rules we just examined are the natural extension and consequence of maximizing our values. XP isn’t really a set of rules but rather a way to work in harmony with your personal and corporate values. Start with XP’s values listed here then add your own by reflecting them in the changes you make to the rules.
- We will do what is needed and asked for, but no more. This will maximize the value created for the investment made to date.
- We will take small simple steps to our goal and mitigate failures as they happen.
- We will create something we are proud of and maintain it long term for reasonable costs.
- Everyone is part of the team, and we communicate face to face daily.
- We will work together on everything from requirements to code.
- We will create the best solution to our problem that we can together.
- We will take every iteration commitment seriously by delivering working software.
- We demonstrate our software early and often then listen carefully and make any changes needed.
- We will talk about the project and adapt our process to it, not the other way around.
- Everyone gives and feels the respect they deserve as a valued team member.
- Everyone contributes value even if it’s simply enthusiasm.
- Developers respect the expertise of the customers and vice versa.
- Management respects our right to accept responsibility and receive authority over our own work.
- We will tell the truth about progress and estimates.
- We don’t document excuses for failure because we plan to succeed.
- We don’t fear anything because no one ever works alone.
- We will adapt to changes when ever they happen.
- Extreme Programming Explained: Embrace Change (Amazon) [English] by Kent Beck, Cynthia Andres
- Clean Agile (Amazon) [English] by Robert C. Martin