yazanash/lab-agile-planning

repo for leaning agile

hey there 👋

👩‍💻 About Me

I'm yazan abo shash

- 🔭 I’m working as software engineer
- 📚 I'm interested in DevOps culture
- ⚡ In my free time I develop my technical skills

🛠 Language and tools

🔥 My Stats :

lab-agile-planning's Issues

Deploy service to the cloud.

As a Service Provider
I need to deploy service to the cloud.
So that I can deliver my work and make service become running

Details and Assumptions

• Deploy the service to IBM Cloud

Acceptance Criteria

Given I have finished my service
When Deploy the service to cloud
Then Service should run perfect 

Must allow multiple counters

As a User
I need have multiple counters
So that I can keep track of several counts at once.

Details and Assumptions

• [document what you know]

Acceptance Criteria

Given [some context]
When [certain action is taken]
Then [the outcome of action is observed]

Need the ability to remove a counter.

As a System Administrator
I need the ability to remove a counter
So that I can remove unused or old counter

Details and Assumptions

• [document what you know]

Acceptance Criteria

Given [some context]
When [certain action is taken]
Then [the outcome of action is observed]

Need the ability to update a counter to a new value.

As a System administrator
I need the ability to update a counter to a new value.
So that I can make counters always updated

Details and Assumptions

• Need to add post URL : /counter/{counter-id}/update/{new-value}

Acceptance Criteria

Given request to update URL
When Update the counter to the new value 
Then the counter should return the new value

Complete deploy service to the cloud

As a Service Provider
I need the service to be deployed to the cloud
So that I can scale capacity with user demand

Details and Assumptions

• Database still needs to be provisioned
• App needs to be pushed and connected to the database

Acceptance Criteria

Given I have deployed to the cloud
When a customer comes to our URL
Then Our service will be available 

Must persist counter across restarts

As a Service Provider
I need the service to persist the last known count
So that users don’t lose track of their counts after the service is restarted.

Details and Assumptions

• we will use a Radis database
• Counter will be stored as name value pair

Acceptance Criteria

Given I have incremented the counter to 2
When I restart the service
Then the counter should still return 2

Need a service that has a counter

As a User
I need service that has a counter
So that I can keep track of how many times something was done

Details and Assumptions

• Need a way to increase a counter
• Need a way to get new value

Acceptance Criteria

Given I have incremented the counter to 2
When I make a call to get the current value
Then it should return 2 as the counter value

Counters can be reset

As a System Administrator
I need the ability to reset the counter
So that I can redo counting from the start.

Details and Assumptions

• Need a way to reset the counter
• reset the counter by post request to URL : /counter/{counter-id}/reset

Acceptance Criteria

Given I get request to reset
When I reset the counter
Then the counter should back to start value