Versions Compared

Old Version 15

changes.mady.by.user Frank Quern

Saved on

compared with

New Version 16

changes.mady.by.user Frank Quern

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Unit Testing
    • Keep the 5 day unit test window - new functionality has been introduced; the time for testing/resolving issues is needed
    • We used an Access db to store a catalog of the transactions we tested by whom and compared to last year
      • concept was good and has value
      • the execution was rushed (the db was not really "production" ready)
      • the tool was a little klugy 
      • better solution should be explored (within SAP, within SM)
    • Should consider storing unit test cases in QC to promote a single consistant cataloging approach
  • SIT/UAT Testing
    • QC - central repository for catalog of test cases
      • Worked well as a catalog for test cases 
      • Great for monitoring execution status
      • Saved preparation time of test "lab" for BAs (cases already in QC and available for use)
    • Test cases for the most part were not ready for QC formatting
      • Cases are/were designed for printing
      • A focused effort updating the cases to be QC formated would be beneficial to the process (requires resources)
      •  

Transports

  •  Transport management processes executed by the transport coordinator need to be documented.
  • Transport freeze
    • IS&T has this processed well defined and understood
    • Could explore another environment to allow development efforts during the freeze (assuming resources are available to do the work during the freeze)
  • Critical transport process
    • A consistent approach should be defined for all similar projects (there have been minor differences from project to project)

Communication

  • Project wiki
    • Great for dates and status, assuming it is kept up-to-date
    • Was used as reference by all IS&T participants
    • Could be used to report cutover status in addition to status phone line, emails, etc ...
  • Status line was used by IS&T staff
  • Frequency of meetings
    • Core Team Monthly meetings - adequate and focused
    • Functional BA - daily meetings during testing phases kept teams focused
  • Did people feel they knew what was going on and what was expected of them? - Yes
  • Other
    • Could utilize WebEx - in light of IS&T moves

...