I need some help
Best of AgileSoftwaredevelopment.com
- Scrum backlog templates and examples
- Simple Product Backlog Example
- Simple Sprint Backlog Example
- Developers Aren't Gonna Read It
- Can unit testing be a waste?
- Six Features of a Good User Story - INVEST Model
- Product backlog
- Performancing Metrics Module
- How to use agile methods for the fixed price contracts
- 7 Tips for Improving the Daily Scrum
- Are you assigning your top engineers to projects?
- Professionalism = Knowledge First, Experience Last
- Top 20 Best Agile Development Books, Ever
- Video tutorial: Managing your Scrum Product Backlog with the help of a simple Excel sheet
- Meet you at XP2006!
- Video tutorial: Managing your Scrum Product Backlog with the help of a simple Excel sheet
- Five risks of solo programming
- Extreme Programming
- Video tutorial: Test Driven Development in practice
- 10 Signs That You're Not Agile
- Five steps for starting the Scrum project
- 10 Principles of Agile Project Time Management
- Destructive bonuses
Subscribe to updates
RSS feedNavigation
User login
Private blogs of the regular contributors
Recent comments
-
James (not verified)
-
Ilja Preuss (not verified)
-
Ilja Preuss (not verified)
-
Model Man (not verified)
Comments
Principles are just high level principles
August 18, 2008 by Artem, 13 weeks 4 days ago
Comment id: 1792
Principles are just that principles. Very useful to bear in mind, but a little far from the concrete list of things to do daily. Methods are ways of interpreting the manifesto and different methods emphasize different things. XP, for example, is focused on engineering practices, while Scrum is focused on the product management level.
Agile methods still are supposed to be adapted to your concrete environment, but it is a way easier to start with the concrete method, than with very general and abstract principles.
Then, IMHO, nowadays the distinction between different methods isn't that high anymore. A merge of Scrum and XP slowly becomes a mainstream called "just Agile". Maybe after Agile became widely accepted as a valid way for SW development people don't have time for many holy wars anymore :)
Quantum Theory and Relativity
August 18, 2008 by peterstev, 13 weeks 4 days ago
Comment id: 1793
Two theories that explain the Universe but appear to be incompatible with each other. Yet both appear to be true. Hence the search for the "theory of everything" which unifies these perspectives.
In projects, it is similar - different people have different needs. There is competition on finding the best way to build the proverbial better mouse trap. There are also other agile frameworks besides Scrum and XP (Lean, Crystal, DSDN...).
It turns out that Scrum and XP were always very closely intertwined. I suspect a big reason why there are two philosophies is simply that the Manager-Types created Scrum and the Techie-Types created XP, each according to their needs.
Today Scrum and XP are (re)converging (and being augmented with Lean). Maybe together they'll get called "Agile", but for reasons I explained in my blog post, I betting the result will be called Scrum.
Post new comment