raganwald
(This is a snapshot of my old weblog. New posts and selected republished essays can be found at raganwald.com.)

Monday, January 24, 2005
  PowerPoint Presentations on Software Development


Here are four PowerPoint presentations I've delivered over the last few years. Caveat: I structured these decks as visual aids for extemporaneous talks. In other words, they do not provide a coherent, narrative story on their own.

(In future talks I plan to experiment with different structures. Some presentations, such as business plans, need to function as stand-alone documents because they are intended to be passed around and reviewed long without your presence.)

Scrum: One Person's Perspective: Shortly after obtaining my certification in the Scrum development methodology (I'm now a "Certified Scrum Master"), I gave this outline of Scrum to the Toronto Chapter of the Software Process Improvement Network.

Evidence-based Software Development Practices: How to develop higher quality software in less time with dramatically less risk by emphasizing the role of collecting and analyzing evidence. This is the cornerstone of my approach to delivering software on time and without drama.

Agile Development or Critical Chain? Yes!: An outline of the Critical Chain Project Management (CCPM) approach and how to integrate it with Agile approaches to software development.

Agile Methods in a Product Development Setting: Sharing my personal experience using Agile methods to develop software products, with particular emphasis on the ways in which product development differs from custom/project oriented work.

Labels:

  9:51 AM

Comments on “PowerPoint Presentations on Software Development”:
Interesting, I often failed explaining this.
# posted by Blogger Gaby de Wilde : 10:13 PM
 
Nice decks! I especially liked your SCRUM deck. One question... How do SCRUM teams handle QA? Your deck has a question and you must have explained verbally during your presentation.

I am currently trying to implement SCRUM within my organization and I am still trying to figure out QA part.

When estimating, do you include QA estimates? Do you do that separately? Do you create a separate backlog item (user story in our case) for QAs? How about time it takes to migrate to next environment (we build web applications)?

Thanks for your help in advance!!

Young Joo
http://blogs.dreamfirst.com/youngj/
# posted by Anonymous Anonymous : 12:37 AM
 
please consult me something about the software development.


i need a demonstration about it. with the power point presentation
# posted by Blogger RAAZ : 4:01 AM
 




<< Home
Reg Braithwaite


Recent Writing
Homoiconic Technical Writing / raganwald.posterous.com

Books
What I‘ve Learned From Failure / Kestrels, Quirky Birds, and Hopeless Egocentricity

Share
rewrite_rails / andand / unfold.rb / string_to_proc.rb / dsl_and_let.rb / comprehension.rb / lazy_lists.rb

Beauty
IS-STRICTLY-EQUIVALENT-TO-A / Spaghetti-Western Coding / Golf is a good program spoiled / Programming conventions as signals / Not all functions should be object methods

The Not So Big Software Design / Writing programs for people to read / Why Why Functional Programming Matters Matters / But Y would I want to do a thing like this?

Work
The single most important thing you must do to improve your programming career / The Naïve Approach to Hiring People / No Disrespect / Take control of your interview / Three tips for getting a job through a recruiter / My favourite interview question

Management
Exception Handling in Software Development / What if powerful languages and idioms only work for small teams? / Bricks / Which theory fits the evidence? / Still failing, still learning / What I’ve learned from failure

Notation
The unary ampersand in Ruby / (1..100).inject(&:+) / The challenge of teaching yourself a programming language / The significance of the meta-circular interpreter / Block-Structured Javascript / Haskell, Ruby and Infinity / Closures and Higher-Order Functions

Opinion
Why Apple is more expensive than Amazon / Why we are the biggest obstacles to our own growth / Is software the documentation of business process mistakes? / We have lost control of the apparatus / What I’ve Learned From Sales I, II, III

Whimsey
The Narcissism of Small Code Differences / Billy Martin’s Technique for Managing his Manager / Three stories about The Tao / Programming Language Stories / Why You Need a Degree to Work For BigCo

History
06/04 / 07/04 / 08/04 / 09/04 / 10/04 / 11/04 / 12/04 / 01/05 / 02/05 / 03/05 / 04/05 / 06/05 / 07/05 / 08/05 / 09/05 / 10/05 / 11/05 / 01/06 / 02/06 / 03/06 / 04/06 / 05/06 / 06/06 / 07/06 / 08/06 / 09/06 / 10/06 / 11/06 / 12/06 / 01/07 / 02/07 / 03/07 / 04/07 / 05/07 / 06/07 / 07/07 / 08/07 / 09/07 / 10/07 / 11/07 / 12/07 / 01/08 / 02/08 / 03/08 / 04/08 / 05/08 / 06/08 / 07/08 /