We are primarily an IT development team of .Net+Java developers who work respectively on components based on these technology stacks only. About few weeks back our team has been asked to follow agile scrum as an organizational initiative. As part of this my team has started having daily scrum standup calls. We also have planning meetings and retrospective now. We do not have dedicated scrum master and product owner in the team however we do have a ‘traditional manager’. We also do not have Kanban board to regularly update the task status. Our team has one confluence page where all tasks are listed. Mostly(for last planning meeting 16 out of 18) tasks are one liner and do not have subtasks even if they are as long as estimated for 5-10 days effort.
Problem(In my view, many team members do not agree to this):
What happens in absence of a Product owner is
- When we go to planning meetings we first start give priority to the tasks as a team based on those one liner task descriptions which in some cases are explained (but not documented) by member who has worked on similar tasks earlier. For some other tasks, we say we are still waiting for requirements.
- As there is no prior analysis of tasks we waste too much time in priority discussion and estimations.
- As these meetings are run by ‘manager’ we still plan everything based on task-people mapping rather than a general estimate.
Whenever I raise above points in meetings, based on my previous experience of agile scrum methodology, I am opposed by almost all team members saying “we will improve in long term, we have just started”. My question is: Is it ok not to have a Product Owner and being dependent on each individual to volunteer to fill details of task(create user stories) on runtime during planning meeting even if it results unclear requirements even after of planning meeting?