Hi everyone, first I would like to thank you for this wonderful platform which is super rich with information.
I would like to ask a question, I was working for almost 2 years as a scrum master for an IT team and I changed my job lately and my goal is to become an Agile Consultant for different projects in my current company; I would like to know what should I do / learn to be more powerfull in this side. Of course experience will bring a lot with time and my experience is already enough for this position but I want to be a master on this side. Are there any good trainings that I can perform which will help me on this side ? I please ask you to answer my question and give me more info on how to improve ! Thank you in advance I really appreciate :)
I have just taken over responsibility as a a scrum master and although i have worked under a scrum team before for a year but i always had difficulty in estimating according to story points. So in my first prokject as a scrum master, I took a risk and though to map story points against hours and it went very well. Here is how i mapped:
Points - Hours
When i gave them a range the team was very comfortable so what i did estimated it according to the table above and in the end they all had a rough time frame then when and how they are going to complete it. I need to know that if it is feasible in long run?
I'm desperately looking for a bit of help! We are a small scrum team who recently turned agile (yay). The previous pm manager preferred using time estimations which was easy for pm's, not the agile-loving dev team. I want to teach my team how to switch to story point estimation and the major concerns of the team are - How do we explain cost to clients per sprint using points? Do we just take the budget total, divide into sprints (based on hours in a sprint) and cost this for a big project?
I have a very reluctant team so any help would be greatfuly appreciated!
Is self-assignment a purely self-directed practice or is a mix of self-directed with assistance from others?Assistance here could be from other team members or Product Owner/Manager/Team Lead/Client/Customer?
I'm currently in a situation where my organization wants to transition to using Scrum for software development and enhancements but we don't have a clear idea as to who will assume which role. Any feedback is appreciated. Thanks!
Should stories be kept in place of requirements to provide permanent system documentation or should a functionally organized set of requirements be maintained as this documentation. Either way, I am trying to figure out the best way to maintain a description/model of the system being maintained that is understandable to non technical and technical staff and provides a starting point for analyzing future changes to the system.