scrum lecture note

scrum -> sprint

daily meeting = = =
accomplish ?
going to do ?
help ?

evaluation

100 points = 100 hours

how many points accomplish ?

how many points move to next sprint ? or put another point

XP – focus more about coding

scrum


XP

planning

– user stories

– release planning

– iteration planning ( reflect )

– project velocity : evaluate progress in project

– retrospectives

testing

– programmer testing ( code code code )

— test-driven dev

– unit testing

— boundary testing

— error handling tests

use test driver ( test suite or set of test ) with stubs

– story testing / acceptance testing ( specify input, estimating output )

– integration testing


testing

– errors

– requirement conformance

– preformance

– indication of quality

testing strategy

testing-in-the-small : unit test

testing-in-the-large : integrate test

guidelines

product req

testing objectives

users

rapid cycle testing

formal technical review

continuous improvement

Testing

top-down

Test parent before write child by simulate child.

bottom-up

do not have concept of overall sys.

test different cluster

sandwich testing

top-down and bottom-up

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s