Hi Nikolay,
You have mentioned that you tend to consider Agile as a set of
practices out of which you can pick out certain items for certain
project.
I did not practice any of Agile methodologies yet. But I plan to try
them out at next opportunity.
Anyway I think I'd rather share your vision.
What I plan to do is just take Scrum routine as a framework and plug
it with valuable practices perfectly described in XP. I have mentioned
important word here: "valuable".
I expect both Scrum Framework and XP practices to be adjustable to
bring maximum value. But what is more "valuable"?
Now I'm getting to the core of my question.
How would you pick out certain practices for new project?
In other words: how do you measure which improvement brings you (or
not) more value?
Thanks,
Roman
Wissenswertes zum Thema PC, Zubehör oder Programme. BE A BETTER INTERNET-GURU!
Addison Wesley Professional - Refactoring to Agility
Pragmatic Programmers - Practices of an Agile Developer Working in the
Real World
Pragmatic Bookshelf - Agile Retrospectives
Pragmatic - Release It Design and Deploy Production Ready Software
Pragmatic - Ship It! A Practical Guide to Successful Software
Projects
>From my own practice I introduce new practice only if there are some
issues that
this practice may help to fix (if it promises that it will help). I
always try to analyze
results of using that practice in different projects and then decide
if it will be helpful
for my project. Never try to introduce practice just for fun. ;) Then
I gain some metrics
as results of using new practice and decide is it suitable for team
and project. From
my point of view if some team members don't like practice and all your
attempts to
show advantages of it was unsuccessful then remove this practice from
your project or
change project/team. ;)
Yahoo! Clever - Sie haben Fragen? Yahoo! Nutzer antworten Ihnen.
I completely agree with you.
On Sep 14, 10:57 pm, "Serhiy Yevtushenko" <syevtushe...@gmail.com>
wrote:
> Hi, Boris.
>
> I have remarks concerning two points:
> 1. XP does have a project management part, it is not only pure engineering
> approach. IMHO, the language of Scrum is more easy to understand for
> business, but as concerning project management practices, there XP practices
> a quite similar, and provide more flexibility to business, than Scrum
> 2. I would agree at all that other Agile approaches are recombinations of
> this two.
> XP and Scrum are most well known.
> Have a look at FDD for very different agile approach. It is definetly not a
> recombination of XP and Scrum
>
> 2007/9/14, Borys Lebeda <borys.leb...@gmail.com>:
>
>
>
> > IMHO, among all Agile practices XP and Scrum are the most valuable to
> > learn. The main reason for that is following:
> > XP is pure development agile approach. It has no standpoints regarding
> > managing development process.
> > Scrum is pure management agile. It's so generic, that can easily
> > be applied not only to software development industy
>
> > The other agile approaches are more or less recombinations of this two.
> > Of course, some of them quite different, but with knowledge of XP and
> > Scrum you can imagine what are others ...
>
Borys,
I think it is a well-know mistake to think of XP as a set of engineering practices only.
Have a look at the set of XP rules there is at least 1/4 relates to PM area.
- requirements areas (user stories come from XP)
- project planning area (release/iteration planning)
- velocity metrics, stand-up meetings (project tracking and oversight area)
Serge,
I think we can go even further and call a Scrum team that does XP engineering practices as an XP team?
Does it make sense?
On Sep 16, 8:49 pm, "Alexey Krivitsky" <alexeykrivit...@gmail.com>
wrote:
> Borys,
>
> I think it is a well-know mistake to think of XP as a set of engineering
> practices only.
> Have a look at the set of XP
> rules<http://www.extremeprogramming.org/rules.html>there is at least
> 1/4 relates to PM area.
>
> - requirements areas (user stories come from XP)
> - project planning area (release/iteration planning)
> - velocity metrics, stand-up meetings (project tracking and oversight area)
>
> Serge,
> I think we can go even further and call a Scrum team that does XP
> engineering practices as an XP team?
> Does it make sense?
>
> // Alexey
>
> On 9/15/07, Borys Lebeda <borys.leb...@gmail.com> wrote:
>
> > 1. Huh, I think we have different points of view on project management.
> > Could you please explain what XP practices you concern to be applied to the
> > project management? Involving customer to the development process can be
> > such standpoint, but XP doesn't stipulate much role distributions in team.
> > 2. Yes, FDD looks quite different ... I should reconsider ...
>
> > On 9/14/07, Serhiy Yevtushenko <syevtushe...@gmail.com> wrote:
>
> > > Hi, Boris.
>
> > > I have remarks concerning two points:
> > > 1. XP does have a project management part, it is not only pure
> > > engineering approach. IMHO, the language of Scrum is more easy to understand
> > > for business, but as concerning project management practices, there XP
> > > practices a quite similar, and provide more flexibility to business, than
> > > Scrum
> > > 2. I would agree at all that other Agile approaches are recombinations
> > > of this two.
> > > XP and Scrum are most well known.
> > > Have a look at FDD for very different agile approach. It is definetly
> > > not a recombination of XP and Scrum
>
> > > 2007/9/14, Borys Lebeda <borys.leb...@gmail.com>:
>
> > > > IMHO, among all Agile practices XP and Scrum are the most valuable to
> > > > learn. The main reason for that is following:
> > > > XP is pure development agile approach. It has no standpoints regarding
> > > > managing development process.
> > > > Scrum is pure management agile. It's so generic, that can easily
> > > > be applied not only to software development industy
>
> > > > The other agile approaches are more or less recombinations of this
> > > > two.
> > > > Of course, some of them quite different, but with knowledge of XP and
> > > > Scrum you can imagine what are others ...
>