Scrum, Spiral, XP, RUP and Waterfall models

[1] Scrum

http://weblog.raganwald.com/assets/scrum.ppt
http://www.otug.org/meeting/slides/20060919-59_Minute_Scrum.ppt

[2] XP

[3] RUP

[*] Introduction to Rational Unified Process
[*] Introduction to Rational Unified Process

[*] A good and thorough overview of RUP; Much of the material seems to be from Rational/IBM.

http://www.eecg.toronto.edu/~jacobsen/courses/ece1770/slides/rup.pdf

[*] Another introduction to RUP;
Also mentions about Spiral Model
http://www.cs.st-andrews.ac.uk/~ifs/Books/SE7/Presentations/PPT/ch4.ppt

[*] How and when Use Cases are done in RUP
Comparison between Data Modelling and RUP
http://www.tcoug.org/Archive/Spring2005/Data_Development_using_RUP_tcoug.ppt

[*] Brief mention and comparison of different agile methods with waterfall
A nice classic slide at the end on how different people misunderstands the problem (tree and tire)
http://itgs.tistory.com/attachment/1264275895.ppt

[*] Incremental Adoption of RUP
Process Landscape (Relaxed, Disciplined, Iterative, waterfall)
ABCDEF (RUP Practices are summarized as ABCDEF which are broken into 2o point summary)
http://www.cardinalsolutions.com/RSCTY/PRESENTATIONS/Cardinal%20Solutions%20-%20Incremental%20Adoption%20of%20RUP%20v3.pdf

[*] Process cocktail - Mixing up XP, Scrum and RUP
(Handling the names in a system - an interesting slide on meeting the 'basic; most common' use cases and handling ALL the use cases)
(Also, very good breakup of how different workflows/disciplines are emphasized in each of the phases - inception, elaboration, construction and transition)
(How the "Best of Breed" in each of the processes can be combined into a new cocktail process)
http://www.netobjectives.com/files/events/download/rup_xp_scrum_pc_030326_ppt.pdf

[*] Adopting the RUP - can it be agile?
The process landscape and how different methodologies fit into that landscape.
Good overview of different artifacts RUP expects in each of the steps.
http://www.williamnazzaro.com/Material/Adopting_the_Unified_Process.pdf

[*] Comparison of RUP and DSDM in the context of Testing
RUP as a buffet - Do you want heavy or light?
RUP as garage or basement - because there are artifacts, we tend to hoard these
http://www.ucalgary.ca/~ageras/wshop/pres/f2003/mg-tw-001.pdf

[*] Free demos from Rational
http://www.rational.com/tryit/rup/seeit.jsp

[*] Introduction to RUP
Good information on how much %age of schedule and effort are spent in each of the phases.
Also, the outline of the presentation is presented in terms of the I, E, C and T (like RUP). That is creative
http://facweb.cs.depaul.edu/jnowotarski/se470/class%202003-04-21.ppt

[*] Managing Process and Methodologies
A good comparison of CMM, RUP and PMBOK
http://www.pmiglc.org/pd/2007symposium/docs/YS_GLC_PMI_Symposium_final.ppt

Managing Process and Methodologies

[4] DSDM (Dynamic Systems Development Method)





NOTES:

[1] Use Cases are described in terms of the language of an end user (customer).
Analysis Models are described in terms of the language of the developers.

[2]
Requirements: Do the right thing
Design: Do the thing right

[3]
Boundary Classes (actions, widgets)
Entity Classes (domain objects) and
Control Classes (C in MVC)

[4] From "http://www.eecg.toronto.edu/~jacobsen/courses/ece1770/slides/rup.pdf"

[*] To illustrate a problem with the waterfall model: Suppose I estimate that the project will take two years, and it really takes three years. At the end of two years, what do I have? Nothing useful works. No partial delivery is possible. Diagrams and models are great, but they can not execute.

[*] Waterfall is conceptually straightforward because it produces a single
deliverable for each step (requirements, analysis model, design model,
code, etc), resulting in a single release. The fundamental problem is that
it pushes risk forward in time, where it’s costly to undo mistakes from
earlier phases. An initial design will likely be flawed with respect to its
key requirements, and furthermore, the late discovery of design defects
tends to result in costly overruns or project cancellation. The waterfall
approach tends to mask the real risks to a project until it is too late to do
anything meaningful about them.

[*] Interesting site http://www.monstersdlc.com/ The site is developed as RUP phases

[*] Waterfall Model is also called Staircase model

[*] All development processes are (a) plan driven (heavy weight) or (b) evolution driven (light weight) or (c) a combination of both