Speaking for myself only, I read every single post, but I sometimes don’t comment if I feel I’m not the best person to respond. Of course, if we all do that, we run the risk of having no responses at all.
I think of it like this:
- Huge bugs may get a special emergency patch
- Big bugs will probably get fixed the next week
- Some bugs might take weeks or a couple of months
- Some (like the accent mark for one of my scouts) might never get fixed
- As for feature requests, open the weekly update email like a Christmas stocking - you might get something awesome that you didn’t even know you would love.
In RSVP reminder emails for calendar events, it would be nice if the email would contain the current RSVP status of the invitee(s) that the email is sent to, so I don’t have to go double-check my RSVP status every time I get a reminder.
How about a list of items that are on the backlog and those that have been requested and will not be considered?
Two things I would like to have added
1)be able to differentiate between a Troop Quartermaster and a Patrol Quartermaster as well as other positions.
2)Be able to enter troop, summercamp awards. Simple text is all we need but please dont force us to keep two sets of books.
You really have done a fabulous job with scoutbook. I hear of people switching to it in droves. We taught it at our University of Scouting. You should be proud of all you have accomplished but please keep going.
Microsoft and the OA Lodge Master system have a more open system. Users can suggest and upvote features. Honeywell software does a similar thing and allows users to both suggest and the direct a small budget of development dollars to those user suggestions.
The BSA will not publish the backlog. The most we are permitted to say is if a suggestion is on the backlog. We cannot predict if or when items in the backlog will be scheduled for development.
Scoutbook already lets you designate a Scout as the Troop or Patrol Quartermaster. When you create the Quartermaster leadership position select N/A for the Troop Quartermaster or the Scout’s patrol for the Patrol Quartermaster.
There are no plans to add custom awards to Scoutbook at least until all national awards are supported.
Microsoft are Honeywell are large corporations with huge development budgets. The BSA is neither.
And the OA LodgeMaster is run by volunteers. The process scales.
So, if I’m reading the responses correctly, the SUAC members decide whether a feature request should be passed on to the development team. If SUAC thinks that something is “worthy”, as it was put, it will be passed along to the developers. At that point, the developers, in consultation with BSA, will decide what gets put on the backlog list.
I’ll need to make sure that the SUAC likes my ideas.
That is not what we are saying. Most requests are added to the backlog. Some are already in the backlog. Others have previously been considered by the BSA and rejected. We try to answer every post for a new request, but we are volunteers and some may get by us because we are busy with our work or personal lives that do not involve Scoutbook.
If there are features that were requested that do not have an answer and you would like to know if it is in the backlog or not, point us to them and we will do our best to answer.
Many requests receive the “on backlog”, “BSA won’t do it”, or “forwarded to developers” responses. However, some just die with no closure.
I’m curious as to the status of this request Remove “Adult Partners” from Pack’s Leader Roster. I was told it isn’t a bug, I concurred that it isn’t a bug and that’s why it was placed in feature request along with details as to how I’d like it to function. Then the topic died after 7 days with no wrap up.
I’ll add that to the backlog but I would not expect there to be any movement on it for the foreseeable future.
Yes, but software development is not a democracy. Roadmaps are one way of handling customer/stakeholder relationships, but not necessarily a good way.
This recent short post from Basecamp, Options not Roadmaps, is a nice reminder of the downside of roadmaps. They’re a small(ish) company that makes their money providing features people will pay to use, but they don’t use roadmaps because they feel the downsides (both in terms of missing customer expectations, and inevitable developer guilt) are not worth it.
I love roadmaps and backlogs too… but they quickly become overwhelming and priorities can change quickly, sometimes daily. Personally, I’m glad I’m not on the BSA development team trying to wade through all the issues and requests (though I’ve sometimes foolishly thought about it )
Without being open about the process people will continue to request the same features over. Also, the process many software projects use is an upvote system to gauge popularity of feature or help determine the severity of a bug.
To move agile, software developers and product owners need quality feedback from customers, unfiltered.
You’re speaking to the choir here, but SUAC aren’t the decision makers for the software roadmap or priorities.
What opportunities are there for qualified volunteers to assist? I understand it would be a large commitment, which adult leaders in scouts already make.
Send an e-mail to email@example.com
Thank you for adding it to the backlog.
I think it would be a good option to have a Troop/Pack organizational map. One where you can select adult leaders only or youth only or both that way you can easily create a document where the troop’s leaders and their responsibilities can be easily displayed.
Potential uses are during a new parent meeting or during ILST.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.