Hi everyone, first I would like to thank you for this wonderful platform which is super rich with information.
Recent Q&A Activity
Suggest me some Agile Automation tool anmes please Agile Automation,
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!
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
I would like to investigate if and how agile priciples can be applied to a TV production enviroment in Denmark. Primarely with a focus on developing a project process that help the production crew navigate in the process when the final TV program haven't been decided from the beginning (outcome is unclear)?
Therefore, does any of you know anything about this - any suggestions for reading or such is also very welcome!
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!
Can anyone help me with an effective self-assessment tool to measure agile maturity in our organisation.
What are the key metrics applicable for an agile project?
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.
Previous conferences of Star West and the agile methodology in general have accepted the concept that testers and programmers are both subsets of the developer category. Is this still the accepted definition or are programmers the only team members that are considered developers.
When product owner express the userstories, scrum team asks for clarification for better understanding.What is the order of actions in sprint planning, is it that tasks of particular user story should be entered in in scrum board or acceptance criteria of the user should be defined first and then entering the details of develeopment tasks with the estimates derived? can you help me with this?