The Einstein Sprint was focused on several Spikes. And we had a very successful Bug Squash Friday
First let's "define" a Spike:
- A Spike is a story that cannot be estimated until the Development Team runs a timeboxed investigation. Some Spikes do end in actual code that can be deployed, but the majority of the time, a Spike is performed in order to have an actionable story for a subsequent Sprint.
SPIKE: Define the Schema for Order Placement and create basic schema placement order
In this Spike we are preparing for the implementation of the CP Ease of Use Epic. Much of the background work has continued whilst we prepare for a UX resource.
SPIKE: Create Flipper Gem
Going forward we want to be able to "easily" "Flip" or "Toggle" on and off various features within the Axon Platform. This Spike lays the groundwork for having the proper tools in place to "Toggle" in Axon. This will be used in the early stages of introducing HBDI Scaling, and in preparing Thinkers to use the Thinker Portal features
SPIKE: Components Library
We now have a populated Components Library that Axon can use as a resource. Using the library allows for consistent use of MANY components, such as buttons, logos, text formats, etc.
SPIKE: Identify key content for a "Journey-less" Launch of the Thinker Portal
The Thinker Portal has been constructed to have "Journey" tiles that a Thinker can walk-through for specific learning objectives. With "Toggling" soon to be enabled, we wanted to determine what content any Thinker can experience and what resources they can use so that the Thinker Portal can be launched without the Journey steps if that is what a Customer prefers.
SPIKE: Ensure existing users activity data is created when they visit the Portal
The current Portal experience is setup so that a Thinker's journey begins with a new Invitation. This Spike was determining what code needs to be in place so that a Thinker who completed any steps of the Journey prior to the Portal's inception, can still use the Portal. For example, a Thinker completes the HBDI in 2016, and now wants to come back to Axon and use the Portal. What code will need to be in place to activate their portal?
SPIKE: Design a system where reports for "Large" groups run in the background
Remember the Spike definition...This Spike was about determining what would need to be in place to allow Axon to run reports in the background for "large" groups. We know the current limits in Axon can be pain points. So we are getting the research done to ease that pain.
Missing Education Codes specific to German are no longer "missing"
Password Error "key" added
And a couple of typos corrected
Bug Squash Friday
Each Friday after a Sprint ends, we have been focusing on Exterminating Bugs. This was a very successful day!
We focused on Report Bugs in order to pave the way for HBDI Scaling and launching the new Reports
See the Slides for a full list
Want More Info?
Google Slides: https://docs.google.com/presentation/d/1Ghk4k1svwCFTv0YtqfP5EL0LZ8eOS1M0NBZA3l0KO2c/edit?usp=sharing
15 minute YouTube Video of Release Overview: https://youtu.be/o2xIuk2hyRA
PDF of Slides in Box https://hbdi.box.com/s/y8ih0pw44nwzoacusu1ez35zhxqhx481
MP4 Video File in Box https://hbdi.box.com/s/y8ih0pw44nwzoacusu1ez35zhxqhx481