Re. Very Simple and Effective Solution for Managing Existing Defects and New Features

Scriptcase 9 General
#1

A very simple tracking system - “Kanban Board” - will be especially beneficial to SC for feature/defect resolution:

The tracking system would have 4 columns:

  1. BackLog - Prioritized new Features and existing Defects (Product Owners Responsibility)

  2. Active - Features/Defects selected from the “BackLog” that can be realistically completed within a 2-week period.

  3. Working - Features/Defects currently being worked on within the “Active” list.

  4. Complete - Features/Defects that have been completed, meeting all user acceptance criteria.

After the 2-week period, a webinar is held with managers, product owners, developers, key sales and selected long-term customers to demo
the software changes.

If all items from the “Active” list are completed successfully, then a working product upgrade (product increment) can be released.

Any software issues discovered by customers can be reported back to SC within an issue/tracking system, where it’s decided whether
to add them to the “BackLog” list.

If some items from the “Active” list are not completed successfully, then they are either kept in the “Active” list, or
moved back to the “BackLog” list. A decision from the product manager will have to be made to decide to release the upgrade with
the features that work, or wait till the next software demo.

During the 2-week period of development and testing of “Active” items (preferably a week into development/testing) SC can hold a meeting to
re-prioritize the “BackLog” list in preparation for the follow-on 2-week development and testing period for up-coming “Active” items.

The “BackLog” list is dynamic, which also means that some items may no longer be relevant, or can be placed further
down in the priority list.

Daily meetings, no more than 15-minutes, can be held between developers, and (if required) product owners to quickly discuss
the status of developing and testing for the current “Active” list. An additional “16th-Minute” can be included for any
new issues or concerns that may have come up during developing/testing.

I’m sure that the many knowledgeable, and talented customers,consultants,re-sellers in this forum would welcome the opportunity and find the time to work with SC
using this process to build a solid and superior product which SC has the capability to be.

#2

Yes, trello would be an option. I have proposed similar things often, including the offer that I would maintain the English bugtracker. For some reason the CEO is unwilling. But the more customers request this, the more chance we make. I 2nd this one.

#3

Glad to hear you’ve made a positive effort to move the product in the right direction, but acceptance must come from within SC for actual change to occur.

If, as you say, the CEO is unwilling to embrace positive and productive change for their flagship product , then he/she should in the interests of those currently impacted:

  1. Step down as CEO and let someone new take over who is open to implementing effective software developing, testing and release methods.
  2. ALSO . . . be unwilling to sell any new copies at this point - get the many significant bugs truly fixed first - then release a free upgrade fix.

What the community can do in the meantime, is demand a free upgrade to address the many significant bugs that plague the product at this point.

Sounds like the company is internally changing directions with SC (perhaps the technical debt is already too high), so it’s best to get a good sense first where they are actually intending to go with this product prior to purchasing anything new.

#4

Scriptcase is not attending this forum in general as this is a user forum. If you have reasons to complain than post your issues directly to sales or bugs at scriptcase. You really are not helping anybody, not even yourself by this. As I posted elsewhere, if you do not like the product then you have a very simple solution. “what the community can do”. I don’t know who the ‘community’ is. If you think that there should be taken some steps you could initiate them yourself. I am a fan of Scriptcase. That doesn’t mean that I don’t have criticism regarding issues, like support, bugtracker and some other things. But nagging the forum is simply not productive. I try to avoid that.

#5

SC, as it is now, is not fit for business use. As a VAR and forum moderator, I would highly suggest forwarding this thread onto NetMake - they are very fortunate that the community of paying and potential customers are still interested enough in SC to report defects and any complaints about the product back to them.

#6

I had been asking them if they have bug tracker to report, but not getting any response. I used send the bug details via email but when they reply they reply via a chat tool which does not bring the original context. They should strive to improve the process to help the customers