Scrum focuses on how to manage the project, especially with regard to planning and evaluation.
XP (Extreme Programming) focuses on technical excellence and quality within the project, as well as on the low cost of change.
Think of each of them as a toolbar, where one set of tools does not create a home. Scrum relies on the low cost of changes to ensure that its speed measurements and its estimates on the other side are accurate, but in reality it does not provide methods for this. XP has much of Scrum in its practice, although some Scrum methods, such as breaking up tasks into history, may be useful for teams that learn.
Even together, you may find that they do not provide enough funds for adaptive planning, large-scale organizational changes, cultural changes, good hiring methods and many other contributions to a flexible team that often does not take into account the methodology.
I would aim for a combination of Scrum with XP, and you would like to take a look at Lean, Kanban, BDD and Feature Injection, while you are on it - there are some useful tools.
As for the start, here are my two main practices:
- Try to deliver some software (showcase or release every two weeks).
- Think about why it was difficult and what to do about it (retrospectives).
Good luck
Lunivore
source share