Re: [scrumdevelopment] Re: Development Case
- Hi Katia,
Have you checked the controlchaos.com and mountaingoat.com websites? Also the agilealliance.org website has a roadmap section that explains most agile methods.
--HubertOn 11/30/05, Katia Canepa <katia.canepa@...> wrote:
Thank you very much for you answers.
They really have help me a lot.
I'm new in Srcum development process but I have learn a lot by your answers.
As George says, Scrum development doesn´t need a hard and formal
For my own purposes I prefer to use this template and make
actualizations when it is too necesary.
I also have read the "Best Practices in Scrum development Process and
XP Agile Software Development". It help me too.
Thanks again for your recommendations.
Best Regards from Perú,
On 11/24/05, Tobias Mayer <tobyanon@...> wrote:
> Interesting post.
> > **Critical is that this document not be used to define the
> > process**, but rather to record the process as it is going on and
> > **after** the fact.
> This reminds me of the 1986 IEEE Transactions paper by Parnas & Clements: "A
> Rational Design Process: How and Why to Fake it".* The authors discuss the
> value of documenting a process after the event - as if it was driving the
> project. Apparently it was somewhat controversial at the time, and upset a
> few people. I read it in the mid 90's. Made immediate sense to me, and set
> me firmly on the agile road.
> The paper is available online at:
> While looking for that link I also came accross this 1999 IID paper by
> Robert Martin:
> which references the Parnas/Clements paper, and again ties in very closely
> with the comments you make in your post.
> I lean more towards the "almost no external documentation" concept now, but
> I do see the value in producing process docs after the event in certain
> organizations. Sadly.
> * IEEE Transactions on Software Engineering archive Volume 12 , Issue 2
> (February 1986)
> George Schlitz < gjschlitz@...> wrote:
> I may get flamed for this...but...I've actually used the RUP
> Development Case on a few of my projects, for two purposes:
> 1) In an organization that has "standardized" on the RUP (which would
> probably make your Scrum implementation a grassroots effort of some
> kind), the development case can be a great tool to keep the process
> police away and to pass audits- resulting in fewer obstacles for the
> team. **Critical is that this document not be used to define the
> process**, but rather to record the process as it is going on and
> **after** the fact. Version control this doc and tag it with the same
> tags as your code and you will be able to effortlessly show such
> groups exactly how the project followed a highly-disciplined process.
> No team member should have to waste time on this- the SM should only
> (I have found this takes very little time once started- only needs to
> be updated much after retrospectives when we implement process
> 2) For my own purposes so that I can see the evolution of my projects
> process over time, and use this learning as a tool on future projects.
> Disclaimer: As others here will undoubtedly state, only documents that
> add value should be used at all. I think that the development case
> can be a useful document, but never to define process- only to record
> it. Under the circumstances described in #1, imho it adds value as it
> helps remove an organizational inefficiency obstacle from the team.
> In #2 I am able to learn more quickly on new projects things that tend
> to not work, and can help future teams come to their own conclusions
> and come up with alternatives- so I will maintain this doc if I can
> find the time.
> --- In firstname.lastname@example.org , Katia Canepa
> <katia.canepa@g...> wrote:
> > Hi,
> > I'm investigating on Develpoment case, a template of RUP that tries to
> > describe all the artefacts, roles and the lifecycle model that will be
> > used in a proyect.
> > Do any one knows the equivalent on srum development? What do you
> > usually use to describe the lifecycle of the process, the artefacts
> > and roles?
> > Please any answer is welcome.
> > Best Regards,
> > Katia
> To Post a message, send it to: scrumdevelopment@...
> To Unsubscribe, send a blank message to:
> YAHOO! GROUPS LINKS
> Visit your group "scrumdevelopment" on the web.
> To unsubscribe from this group, send an email to:
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
------------------------ Yahoo! Groups Sponsor --------------------~-->
Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...
Yahoo! Groups Links
<*> To visit your group on the web, go to:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to: