@SteveTwips What bad means Steve? I have 12 teams one projects and track work in ado and can see the overall progress by release. Portfolio and user story levels.
The Agile ceremonies are important to follow but they are releted to a particular agile framework. Hovever, the most important is the Agile mindset (values & principles) to share across company or at least within the whole Team. Agile manifest founders came from xp, scrum, lean..
@allenholub The idea is to do priorisation of 100 features lets say, based on their impact on the metric that i m as pm is in charge of. Metrics are changing in function of stage of life of the product.
@allenholub I m just following PM training just for me to better help me po/pm. What i m doing most of pm doesnot. I have hiérarchy of metrics as mindmap. Metrics are at company level then i create them at my service level, 4-5 levels. Then 1 st sorting of ideas, then 2nd as impact mapping.
Find your team lacks initiative?
Review your\your organization management style... your are certainly caught in directive way of management... going to coaching style where appropriate will help!
@jurgenappelo What helped me was ICF coaching course, normal coaching not agile or business. After i could deeply understand my objectives, prioritize them, validate them. Applied the knowledge on my teams ,greatly helped.
@allenholub Agree. I do believe one should not apply a framework at call it like now all works on scrum or safe rules, instead i promote to craft your own agile process taking the best ideas and continiously improving it. Do not lock your team in a framework bondaries, that kills agile.
@ArtemGoutsoul@allenholub Try to have your user stories small say all 4 or 5 sp
Then you do not need estimations as can use flow metrics.
Flow metrics... sell them the number of us to be done. Etimate end date using throughput or team capacity to deliver by a given period and cycle time.
Before thinking to choose a tool take a whiteboard or a pen/paper to draw your prosess first. Then choose ypur tool. Never try to do the inverse. Many of us do, the most of us ....
@allenholub Agree. This is actually the case all is organized by value responding to customer painpoints in one tool. Then in jira, the tool n 2, we have this subject area epics to structure work. Connection between the 2 are more mental.
Ex of not applied 1st process, then tool principle.