How to provide feedback on the Sprint Capacity Analysis application

[Dave]

Hi all, 

I'm an Atlassian employee and I recently published the "Sprint Capacity Analysis" application to the Atlassian Labs space (see https://marketplace-admin.internal.atlassian.com/apps/1238160/sprint-capacity-analysis )

This is a free application and is a personal side-project of mine that my team (and others) within Atlassian are using. It leans into agile / scrum practices that I've developed over many years of software development that I've written about here: https://community.atlassian.com/forums/Contributors-articles/Pragmatic-Agile-Sprint-Planning-Work-Item-Counting-Capacity/ba-p/3055797 

One of the challenges with an Atlassian Labs application is in providing support, it's a free application that I build in my spare time but am personally committed to support for as long as there is interest and I'm able to.

I received my first review on the marketplace which pointed out the challenges with documentation which I would like to address.

I'm keen to get feedback on the application, have bugs reported and learn about how teams work. Unfortunately I can't provide a dedicated support channel (as we don't want to create the impression this is a fully supported application) however it was suggested that I could subscribe to a tag in this group that anyone can post to and I'll answer as best I can!

So if you have any questions feel free to tag a discussion or question with "sprint-capacity-analysis-app" and I'll jump in as soon as I can!

Thanks all!

Dave

[Dave]

FYI @Cassandra Fitzgerald ... I just wanted to tag you in this thread as you added the review to the app that prompted this discussion and I wasn't sure if you'd get notified about my reply to it.

I'd be very happy to answer any questions you have about the application!

Thanks,

Dave

[Danno]

@Dave , I just saw your recent post regarding an update to this app. I will add it to my site and start evaluating it, and provide you with feedback. This is the first time I've stumbled onto the Labs area. I like the idea of devoted Atlassian team members creating useful add-ons.

[Tracy Skelton]

Hi Dave!

I recently stumbled across this app and have been testing it out as a potential replacement for a paid add-on for sprint capacity planning. I wanted to see if there is any additional documentation on how your team is using it to plan sprints? (I tried the links above but am receiving error so not sure if this answers my questions).

I think for my use case and how we plan what might be helpful is a way to click into stories while in planning view or be able make adjustments to assignee/points/etc. As well as being able to face up see who is assigned and an estimate of how filled their sprint is. 

I know this is something that you've been working on on the side for your team but can definitely provide additional feedback on how my teams might use a tool like this if it is your interest to add enhancements/updates.

Thanks so much and have a great day! 

[Dave]

Hey @Tracy Skelton 

Thanks for post... I completely understand what you're describing and it's something I can explore, but I don't think that it's easy to open the issue view model from within the Forge app (but I'll double check this).

Usually when we're doing sprint planning as a team (typically over zoom because we're all remote workers) the host will have one tab in their browser showing the backlog and one tab showing the app. That allows us to quickly reference which issues (when you click on the sprint and see the details, you can view the work items currently assigned to the sprint).

Ideally it would be great to be able to manually move them, but that would require reloading and calculating the data which might make things a little slower to use. 

In our planning sessions we'll do the following:

1. Review the past sprint and update the capacity for any unplanned absences (e.g. sick days)
2. Update the next sprint with planned absences (vacations, public holidays)
3. Review the proposed number of work items we should be including in the next sprint
4. Switch back to the backlog view and make some changes to try and match the the velocity / issue count
5. After making some tweaks we'll then reload the app and check the next sprint looks achievable

There's no doubt that it would be nicer to get a bit of a tighter loop and integrate the planning with the analysis.

I'd be super keen to hear how you get on with the app... if you hit any problems or have any suggestions for features then please let me know!

Many thanks,

Dave