3

Try to bring the work to you I would suggest to create a Kanban board for yourself and allow people the option to give you work. Have columns like: To do| In progress | ... | Done -----|-------------|-----|------ | | | You take work from the top of the "To do" column and you work on it. Once it's done or you have more ...


2

In Scrum, the Product Owner has limited power to improve quality. I see 2 potential actions: Manage the Product Backlog accordingly. If the timeline is too tight, try to find items which can be potentially removed or replaced by a simpler but sufficient solution. Write more accurate user stories and acceptance criteria. While the tumb-rule suggests not to ...


2

It depends First of all, you need to aquire project management and Scrum knowledge if you want to be a PM or a SM. It goes without saying that you need to put in the effort to learn and aquire the skills that can differentiate you from other candidates applying for the same jobs. A degree and an MBA aren't worth as much these days compared to some time ago. ...


1

Based on what I've read (e.g. here) the Independent Technical Review is not so much to check the quality of the software - that's the job of your QA team. It's also not because you don't trust your dev team; why would you hire people you don't trust. Besides, it sounds like they delivered a product that works, with minimal bugs. The Independent Technical ...


1

I suggest you research Total Cost of Ownership (TCO). You'll find quite a few checklists and examples to give your some ideas. You could start here: https://www.cio.com/article/3005705/calculating-the-total-cost-of-ownership-for-enterprise-software.html


1

It's pretty easy. First thing you have to understand that everybody considers you a free resource. Nobody cares what you do for other projects as you are free. That is why it's easier to dump a task to you then to do it themselves. You should follow those simple steps (you need some task management system for that like Jira or Trello): Start the formal ...


1

I struggled with the same issue, but was unable to find a suitable answer. As a work around I created a graph to show the amount of tasks and their status in the current sprint. A spike would appear in the category 'new' (for PBI's) or 'to do' (for tasks). For clarity I separated the PBI's and bugs (which I see as a high level) and the tasks (which I see as ...


1

especially when the quality of the work done is not optimum. How do you measure the quality of work ? "Optimum" is ambiguous in my opinion. Do you have DoD defined for the work/stories/fixes ? So how can a product owner or scrum master best manage the reoccurring fixes during a sprint? If you feel that recurring fixes are happening due to ...


1

especially when the quality of the work done is not optimum This is the area I would focus on. Raise quality and the impact of testing is reduced. Things like test automation and continuous integration can really help. So how can a product owner or scrum master best manage the reoccurring fixes during a sprint? I'm assuming you are using the Scrum ...


Only top voted, non community-wiki answers of a minimum length are eligible