I am a die hard golfer and have been my entire adult life. My golf buddies and I are competitive to a fault. It is not just about who wins, but who has the best stats. I created this Google Sheet to make it easy for us to track our scoring statistics and thought I would share it with those of your are also passionate about golf and rubbing your success in your cohort’s face!
Overview
The Golf Stats Dashboard allows you to track scoring statistics for any number of golfers and any number of courses. It is not bound by an individual season allowing you to see your progress over time. …
UPDATE: I have since incorporated this feature into the EJQT. You can find the details here.
I have had a number of requests to allow the EJQT to automatically execute the selected query on a daily basis to make it more like a reporting tool. That is really the role of the LAD and LSAD tools which both have the automatic execution and I would prefer not to reinvent the wheel.
With that said there is a relatively easy way that you can add in the automatic execution yourself. Google Apps scripts uses what they call Triggers to allow scripts to handle various types of events. One of the event sources is time. Based on a schedule you can tell the Trigger to execute a function in the script. …
Just a few quick updates:
- There was an issue with the Enhanced Jira Query Tool when attempting to query fields that were of type Option. The type was not defined in the Available Fields sheet. This has been corrected. The updated version is on the Agile Creatives website on the Tools page
- Google Apps Scripts, which is what all the tools are programmed in, now defaults to the new V8 runtime when you create a new Google Sheet or copy and existing one. The tools currently are not compatible with V8 and will throw an error when you attempt to use them. You can easily switch back to the previous version(Rhino) using the following two steps: 1) From the Tools menu in the Google Sheet select Script Editor. …
I have made a number of updates to the LSAD that make it easier to diagnose configuration issues as well as provided a work around for an issue with the Jira sprint field:
- Specific errors will now be thrown when there are no sprints returned for a given board id, there are no sprints within the configured time range, and/or there are no issues returned for a given set of sprints. This will make it easier to determine what specific configuration is in error. Previously the errors were generic making it difficult to determine the root cause
- A data validation was added to the Jira Instance URL configuration that will prevent the protocol prefix (https://) from being included in the entry. Some people didn’t realize this and had gotten stuck so now the validation will prevent the prefix from being…
I published this article a couple of years ago on LinkedIn. Thought I would post it here as well…
When I see a Scrum team struggling one of the first places I look is the Product Owner (PO) role and more often than not I find the problem or at least part of it. Too often teams and organizations fail to understand just how critical the PO role is to the success of the team and the product.
The PO role is not an an administrative role it is a leadership role. While all the roles on a team are important the PO role is probably the most essential. Other than for very small or simple products or services the PO role is a full-time gig and not something that should be handled by a group or committee. …
About
