Versions Compared

Key

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

...

  • The amount to be paid = (hours + minutes worked) * hourly rate
  • The check in time and check out time must be specified. These times must be specified in the following format HH:MM [<AM|PM>], if AM|PM are not specified AM is assumed, otherwise 24hr notation may be used or any combination.
  • The hourly rate is a decimal value
  • The hours worked should be as a decimal value

You will not be responsible for the extrating of the data from the legacy system only the correcting and formatting of the times and, calculating the hours worked and how much they should be paid

Acceptance Criteria Statements

...

That's a really difficult question to answer.  But let me try!  I would start by saying the criticality of the application would be a major driver.  I'm going to divide the world into two groups criticality and complexity.  I'm using criticality as a measure of importance and value to the organization.  I'm using complexity as a measure of how difficult it will be to implement/realize the use case/story for which the scenarios are related. DrawiobaseUrlhttps://celestialconsulting.atlassian.net/wikidiagramNamecriticality-vs-complexitywidth762.5684689391128pageId94699579height575.5revision5

Image Modified


How to read the graph

Each quadrant represents a level a complexity and criticality.  

...