Scrum: How to work on one story at a time
I was nominated as scrum master in a new formed scrum team. We have already done some sprints. In the beginning I tried to make my team to work on one story at a time. But it didn’t work.
My team had difficulties to distribute the tasks in a way that they can work simultaneously on one story. Maybe we are doing something wrong?
Task ownership with WordPress – CSS – Designer or Developer?
We have a dispute regarding who owns which tasks when it comes to the CSS on our live site.
Should I fix small issues or let them go? [closed]
It is not guaranteed that I find a solution.
How to organize projects in Redmine? [closed]
Closed 11 years ago.
Simple task framework – building software from reusable pieces
I’m writing a web service with several APIs, and they will be sharing some of the implementation code. In order not to copy-paste, I would like to ideally implement each API call as a series of tasks, which are executed in a sequence determined by the business logic.
Simple task framework – building software from reusable pieces
I’m writing a web service with several APIs, and they will be sharing some of the implementation code. In order not to copy-paste, I would like to ideally implement each API call as a series of tasks, which are executed in a sequence determined by the business logic.
Simple task framework – building software from reusable pieces
I’m writing a web service with several APIs, and they will be sharing some of the implementation code. In order not to copy-paste, I would like to ideally implement each API call as a series of tasks, which are executed in a sequence determined by the business logic.
Simple task framework – building software from reusable pieces
I’m writing a web service with several APIs, and they will be sharing some of the implementation code. In order not to copy-paste, I would like to ideally implement each API call as a series of tasks, which are executed in a sequence determined by the business logic.
Simple task framework – building software from reusable pieces
I’m writing a web service with several APIs, and they will be sharing some of the implementation code. In order not to copy-paste, I would like to ideally implement each API call as a series of tasks, which are executed in a sequence determined by the business logic.
How can I introduce QA and break it into parts for various people?
I was recently asked how to do this, specifically: