Bob Hartman
Forum Replies Created
-
Interesting problem. We at Agile For All are pretty much tool agnostic and don’t keep up with them because there are so many, but some of this seems like stuff Jira should do out of the box. I’m guessing the second one you list would require a custom field so you know what work type it is, but then you should be able to generate information from that.
Worst case you could just take an hour per sprint and transcribe everything into an Excel spreadsheet and manipulate it however you want. It can’t be that much data on a per sprint basis but maybe I’m wrong.
-
I’m not big on directly answering questions like this without some context of what has been attempted and what the results were. I like to have people think and try some things that seem reasonable so we can see what happens. If it doesn’t work, then a more knowledgeable person may be able to make suggestions. So…
What have you tried so far and what happened when you did those things? Let’s work through this a bit more.
-
@Baylor What you are looking for is really a Certified ScrumMaster course. While what you are doing sounds like Scrum, it really isn’t. Having that many issues pop up during a sprint is usually a sign of a team not doing sufficient backlog refinement prior to the sprint starting. You would learn about this topic and many more in the class. Our list of classes can be found by clicking on Agile For All then Upcoming Courses in the top menu of every page on this site. Or you can go directly there by clicking this link (at least I hope it becomes a link!) http://agileforall.com/upcoming-courses
-
Every time I read this thread I love it! It is so much fun to learn about new people.
-
@thambu my problem is you are separating testing from development. You end up with two “tickets” when in fact, there should just be one. Instead of “develop ABC” and “test ABC” as two tickets, it should be “do ABC” as one ticket. There can be separate tasks in that ticket for developers and testers. The team should be estimating together to come up with reasonable numbers for how long it will take to get the entire ticket (user story, product backlog item, or whatever it is called) to “done”. Separating things out creates a waterfall situation where one group does the work and passes it to another group, rather than the agile way where the group works together.
-
Any Product Owners out there want to jump into this thread? I’ll have to take some time in the next couple of days to find the books I really like. It’s been a while since I made a list of them and some new ones have popped up. And I’m really interested in what the community has as ideas!!!
-
Hey @JoelMc do you mind us asking what you were searching for on Google when you found us?
-
Thanks, that’s useful information. Have a great day!
-
@Nicky do you mind if we ask what sort of Google search you did to find this site? We’re always looking for how to make it easier to find us!
-
It is awesome to have you here @Caia. Feel free to ask questions. We’ll try to get them answered!
-
@Jacob Ferrin I’m looking forward to seeing you in CSPO class next week!
-
We’re glad you are here @Brian Christensen
Hopefully you will really like the class next week. I’m looking forward to having a fun-filled, engaging and deep learning two days!
-
We put the timezone in because the class is live, instructor-led and will be during general business hours in whatever timezone is listed. So yes, it does matter.
The course is instructor led with plenty of time for questions.
-
During backlog refinement the team is trying to fully understand the backlog item. If there is a dependency, then it should be brought out during backlog refinement so it can be examined and determined how to handle it. This situation sounds like the team is using something completely foreign to them, in which case backlog refinement would have pointed out the risk and perhaps a solution would have been to do some research into what would be required. It should be a rare occurrence when a team is surprised during a sprint, not a common occurrence (as it seems to be in your case).
If you aren’t doing backlog refinement today, then you would not have experienced the power of it. It is a piece of core Scrum for a reason.
Here is a video I did about it over a year ago https://www.youtube.com/watch?v=M06U2wo6s0s
-
Welcome @Mici we are happy you are able to join us. Feel free to ask questions. We’ll try to get them answered. Also, if you don’t mind answering one more question, what type of continuing education are you interested in? We’re going to be putting together some smaller on-demand courses in 2022 so I’m very interested in your answer!
-
Pete, who is your manager that I can thank for sending you my way???
-
Now that’s what I call expert advice! 🤣
-
@tim that is a good list. I would probably pay most attention to #8, #1, #3, #4 and #5. To me those are the best ones on that list. #2 and #9 are a bit dated at this point.
-
Great to have you hear @Manny! Also interesting that you found us on LinkedIn. That is good information for us to know.
– Bob –
-
@Jeffrey Middaugh it is good to have you as a member of the community. It will be fun having you in class this week. Hopefully I’ll do a good job!
