Please enable JavaScript.

Coggle requires JavaScript to display documents.

Agile (ASD ( Adaptive Software Development) (phases in life cycle…

- - - - to improve each other's creative skill
- - - - product backlog
        
        list of requirements
      - sprint backlog
        
        work units required in a sprint
    - - work units that fit a time box(30 days)
      - changes are not introduced during a sprint
      - shippable product at the end of a sprint
    - - what did you do since last meeting
      - what obstacles are you encountering
      - what do you plan to accomplish by next meeting
    - - deliver software increment to customer
  - - - the whole project
        
        sum of requirements implemented in this sprint and before it
- - - - using incremental prototyping
  - - - remaining detail implemented later
  - - - check if app is viable for dsdm
    - - establish requirements that allow app to provide business value
    - - create incremental prototypes
        
        that are later evolved to the main app
    - - review prototypes to ensure they provide business value
    - - places latest increment in operational env
      - increment: operationlized prototype
- - - - Relatively high: early
      - Relatively low: later
    - - Low: early in the project
      - High: during a later stage. Eg during validation testing.
- - - - <action> the <result><by for of to> a <object>
        
        add the product to shopping cart
- - - - all unit tests executed
      - acceptance tests for testing customer visible functionality
    - - follow KIS principle
      - design provides implementation guidance
      - use CRC ( Class responsibility collaborator) cards
      - for difficult problems, create 'spike solutions' - a design prototype
    - - assign cost
      - group stories for deliverable increment
      - create user stories
      - make commitment
      - determine project velocity
    - - Encourages pair programming
      - Write unit tests before coding
  - - - design for today, not tomorrow
- - - - Ex. communicate information to customer
    - - each model should provide different aspect of the system
    - - remove models that are not used anymore
    - - it should provide useful content even though it might be flawed
    - - understand their strengths and weaknesses
    - - this approach should be adapted to the needs of the team
- - - - secondary goal: setting up for the next game
    - - resource limited cooperative game of invention and communication
      - family of process models
      - use reflection workshops