New Tool

Good chance people recognize the tool in the screenshot. We’re shifting our planning out of a custom Google Sheets document and into Jira. Why the change? Easier to access, easier to work with, and most importantly, it’s a tool we both use for work at this point so we know it pretty well.

Last Meeting

This past meeting we tweaked our original list of goals for v2.0 and decided on priorities. We also decided that meeting weekly for this stretch of Thursday night is working well and we’ll continue for the foreseeable future. We may change to a less frequent cadence once planning is complete, but until we get everything planned we will continue at the weekly pace.

Next Meeting

Much like the last two, we’re going to continue planning this week. Now that we have overall goals, we need to setup the stories that define them and the bite size pieces we’re going to use to eat the elephant. Planning continues, same bat time same bat channel. Thursday night 9:30 – 10:30 Eastern (6:30 – 7:30 Pacific) on our Discord server (leave a comment if you would like to join us). If you don’t currently have access and would like it, please either reach out to one of us directly or post a comment and we will send you an invite.

Thanks again for all of your continued support! #ExerfyYourGames

The post Planning a way forward – Setting Priorities appeared first on Model B.

That hiatus ends this week. We learned much during the v1.0 Alpha and in the time since then. So much that we have come to realize we need to iterate on a couple of specific elements in the design to make Holoseat more robust and more affordable.

With that in mind, we will be holding a v2 development kickoff meeting this Thursday night 9:30 – 10:30 Eastern (6:30 – 7:30 Pacific) on our Discord server (leave a comment if you would like to join us). We will be setting up our Jira project by defining our release goal(s) and setting the top level features (detailed agenda below).

Agenda

1. Define goal(s) for v2.0
2. Capture v2.0 Features
3. Prioritize v2.0 Features
4. Establish meeting cadence

Thanks again for all of your continued support! #ExerfyYourGames

“Microphone head” by sparetomato is licensed with CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/

The post Testing… testing… is this thing on? appeared first on Model B.

With our work transitioning from development to testing and marketing, we have shifted from Scrum based sprints to Kanban based iterations.  This post will cover the results and lessons from two Kanbans, 1.1 and 1.2.  As always, you can get all the details by from our weekly stand ups.

Review

Agile reviews are an opportunity to hold ourselves accountable by identifying how much of what we planned we actually completed.

Claiming Done

• Setup alpha.holoseat.com and back end surveys to capture feedback from Alpha Testers
• Published first Alpha Tester guest blog post, Working Out with a Wargen in World of Warcraft
• Opened weekly stand up meetings to Alpha Testers
• Began relocating corporation to address logistics issues with current location
• Conducted research on better utilizing social media resources to build following ahead of crowd funding campaign
• Wrote a Holoseat Testimonials page (thanks to our testers for sharing their stories)
• Started the “How I Holoseat” blog series to share testimonials on the blog
• Research influencer marketing
• Submitted Holoseat to Hackaday

Not Claiming done

• Relocation of the corporation (blocked on state government)
• Holoseat trademark (blocked on relocation of the corporation)
• Build Facebook community around Alpha Testers (dropped from plan, going to rework the plan)
• Wrap up final paperwork related to Alpha Test

Retrospective

Agile retrospectives are the means by which we “inspect and adapt”.  This is our chance to promote what works and adjust what does not.

What went well?

• Great first guest blog post
• Good use of research into moving businesses between states turned into huge time savings in the process (domestication vs reincorporation)
• Good use of inspect and adapt mid-iteration around use of social media when planned activities were not working
• Did a good job of sticking to PY19 goals of focusing on marketing and business (notice we did not claim done on any technical items in this iteration)
• Happy with how the testimonials page/How I Holoseat combo turned out
• Our unfinished work is predominantly items that were blocked or we reworked the plan (vs just things we did not get around to)

What did not go well?

• We really must improve how we go about doing social media and marketing
• Uneven distribution of workload due to extenuating circumstances

What can we do better?

• Bring a marketer on board
• Try moving to 2 stand ups per week during PY19 Kanban 2.1 and evaluate if this helps with workload distribution

The post PY19 Iteration 1 Review and Retrospective appeared first on Model B.

Alpha Patch 1 – Sensor Housing Fix

Before Patch

After patch

The post First Patch Issued for v1 Alpha appeared first on Model B.

Tone Ring Half Assembly Instructions

Product: HS-03: 18 Pole Tone Ring Half

The post Just Posted Assembly Instructions for the v1 Alpha Tone Ring appeared first on Model B.

Never again let the broken threads of your 3D printed parts ruin your day. Use heat-set threaded inserts when fastening parts together.

Source: Fasteners for 3D Printing – Using Heat-Set Threaded Inserts | MatterHackers

The post Fasteners for 3D Printing – Using Heat-Set Threaded Inserts | MatterHackers appeared first on Model B.

While 2017 was a huge success, I was completely surprised by the specifics of how we accomplished our goals.  As a quick recap, here are our goals for 2017.

1. Finalize the hardware design needed to address the key feedback from demos at SyndCon 2016.
2. Run a private beta test program for Holoseat to vet the design before releasing version 1.0.

So, what happened?  We started the year with some less than great technical and business assumptions.  On the technical front, we were convinced we needed to upgrade out of the Adafruit Feather to a full on system-on-a-chip controller board.  And on the business side, we allowed ourselves to be caught up in the siren’s song of crowd source campaigns too soon.  Sadly, these assumptions took us down rabbit holes most of the year.  Fortunately we caught ourselves in time for a great SyndCon 2017.

Finalizing the Hardware Design

We started 2017 chasing down two seemingly unrelated design issues:  profile management and Holoseat’s sensitivity to pedaling activity.  Profile management covers things like trigger cadence (how fast an individual has to pedal to trigger walking).  And Holoseat’s sensitivity to pedaling actions impacts how long it takes Holoseat to recognize changes in pedaling.  Bryan and I focused the first half of 2017 on addressing profile management.  This effort took the form of redesigning Holoseat around a brand new family of development boards:  the CHIP/CHIP Pro.   Moving to the CHIP boards involved redesigning basically everything about Holoseat and led to an enormous amount of scope creep.  I could write pages retrospecting how exactly we got to that point, but that’s another blog post.

We were still testing the fundamental technologies we needed for a CHIP based Holoseat with only 8 weeks to go until SyndCon.  To say we were off plan is an understatement.   Things turned around when Bryan took charge of designing a custom tone ring to use with a new sensor.  Within four weeks we had a working prototype for these sensor upgrades, versus the four months we spent working on the move to CHIP.  More importantly, the new design’s improved sensitivity yielded unexpected benefits.  Namely, Holoseat was now responsive enough to calculate trigger cadence in real time.

We quickly realized this “adaptive cadence” capability meant we could drop profile management and go back (again) to our original Feather based design.  After conducting additional testing we also concluded we had arrived at our minimum viable product (SyndCon prototype shown above).  And what became of all of the effort we put into researching the CHIP boards? A large chunk of that work went into mastering Python in IoT applications. It didn’t take us long to realize the bulk of that work could be re-purposed into the development of a brand new, and feature complete, desktop configuration app. Further, thanks to Python’s portability, the same app will run on Windows, Mac, and Linux. And should we need to revisit a CHIP based Holoseat, it will work there, too.

Setting Up Our Testing Program

Great Read for OSHW Start Ups

One of the things we have to keep in mind is Holoseat is more than just a technical project. It is also a business and an investment of our time and money. This means we divide our effort between technical and business matters. For example, 2017 included research into preparing for and running crowd source campaigns. One of our conclusions from this research was we were not ready to run a crowd source campaign in 2017. We simply did not have a large enough online following to form the foundation of a successful campaign.

What we did have was a supportive core of fans asking us when they could get their own Holoseats. The value of this core group of supporters became apparent to us after reading Building a Hardware Business.  The authors discuss different growth strategies including building on a small core of passionate users.  This strategy resonated with us and we decided it was time to organize our core fans into a testing community.

So, we put together our Alpha Test Program and offered 5 slots at SyndCon. We came home with 8 deposits for Alpha units. One fan even tried to give us his money during our annual Holoseat presentation! #winning  Having 8 high quality testers is going to be significantly better for us in the long run.  Now the race is on to complete v1 Alpha so our testers can get their hands, er feet, on Holoseat.

Stay tuned for Part 3 where we lay out the 2018 plan and cover how we are doing so far.

The post There and Back Again: An OSHW Project’s Tale – Part 2 appeared first on Model B.

Alpha Prototype Progress

First, we’ve got our prototyping done for most of our design changes.  And, we have some nice pictures so you can see for yourself how we are coming along.

The article picture shows our updated prototype setup on a breadboard using the new TRRS cable to connect the controller to the sensor and the new Cherry MX key switch for enabling Holoseat.  Using a network jack (look in the upper right corner) we connected it to the existing setup from one of our SyndCon demo units and I used it for a few hours.  Worked just as smooth as our assembled units, so we know these changes didn’t mess with a good thing.

Speaking of the key switch, did we happen to mention that we’re doing a custom keycap with the holoseat h?  Here’s what it looks like lit up on our couple of test key switches we were trying out:

That covers the main electronics review.  But what about the little bit of magic that pushed our accuracy up to the point where everything smoothed out?  The tone ring has gotten a bit of a makeover too.  We have split it into two pieces.

Tone ring parts, fresh off the 3D printer

Assembled tone ring

Why’d we split it?  We wanted  to have a cover over the magnets so they couldn’t come out.  It wasn’t an issue during the demos, but we felt that was a poor choice to have them pressure fitted like they were long term.  These are straight 3D prints from the drawings, so they’re still a little rough looking.  But you can get an idea for how the final tone ring will work.

Next Steps & Getting Involved in the Alpha

So that covers our progress so far.  But it still leaves quite a bit left to do.  And the majority of the remaining work is less about hardware development and more about getting ready to take on testers, getting our redesigned desktop software into shape, and sorting out a few things on the business side.

Moving forward what we need from those of you who follow this blog is some help.  Here’s a few spots where can make a difference for Holoseat:

• Do you have some ideas for questions we should be asking our Alpha testing users during the test program?  Post them here <link to google form for submitting questions>.
• Enjoy 3D modeling?  We could use your help porting our mechanical designs from Solidworks to  Autodesk Fusion 360.  Our volunteer mCAD modeler prefers Solidworks, but it is not an open platform, so we need to move our mCAD models.  If this sounds like something you would like to help out with, please fill out the volunteer form indicating you want to help with mCAD <form link>.
• Do you have a knack for python and enjoy development? Consider volunteering to help with the desktop application.  Again, the volunteer link is here.
• In the DC or Blacksburg, VA area and want to help with final assembly and shipping?  We’ll take volunteers for that too!  I’m guessing you know where this is going.

TL;DR

We’re behind (no Holoseats for Christmas), but we’re moving forward at a good pace.   We would rather be a couple of months late with a Holoseat you will love than ship something substandard on schedule.

Looking at the novel I’ve just written, it’s time to get back to work.

The post Alpha Status Update appeared first on Model B.

This past February we posted about our progress during 2016 and our plans for 2017. In that post we identified two key goals for 2017, to be completed by SyndCon in August. Those goals were:

1. Finalize the hardware design needed to address the key feedback from demos at SyndCon 2016.
2. Run a private beta test program for Holoseat to vet the design before releasing version 1.0.

So how did we do? We got back from SyndCon a few weeks ago and I am happy to report it was a complete success. But I must admit, the way we achieved that success and the Holoseat we took to SyndCon were quite different than what I envisioned when we wrote that post back in February. To understand why it is best we take a look at each goal one at a time.

Goal 1 – Finalize Hardware Design

Two pieces of feedback drove the hardware design work called for in the first goal. The first piece of feedback was an unanticipated need to tweak Holoseat’s settings every time we changed players or games. One setting in particular, trigger cadence – the pedaling speed required for Holoseat to recognize a player is walking, took half of the demo time to dial in during most demos. Our intended solution was to migrate from an Arduino controller board to a significantly more powerful one, the CHIP Pro.  This change would enable on board management of player specific profiles. These profiles would capture each individual player’s settings per game enabling players to switch out Holoseat settings as easily as they switched between games.

The second piece of feedback driving Goal 1 was a desire for faster response times from Holoseat.  Take a look at the video below to see the v0.3 response times for yourself.

While not captured in the February blog post, we had a line of research lined up to address this request.   But, we prioritized this research lower than incorporating the new controller board. The irony of this decision will become apparent in Part 2 of this series of blog posts.

Goal 2 – Run the Beta Test

How would you fund the development and manufacturing of a beta design for a new hardware project? If your answer is “KickStarter!” you are very close to where we were in our thinking last February.

Sadly, running a successful crowd source campaign takes more time, and a greater social media presence, than we had in 2017. Thankfully we came to this realization (through careful research) before we got too far into the year. At the time we thought we were completely blocked on this goal.  So, we spent most of 2017 assuming we would have to wait at least a year before we could engage outside players as testers.

But in agile projects like Holoseat, being blocked does not mean things are hopeless. Blocks are meant to be resolved and once they are you can get back to working on implementing your plan. Sometimes the trick to resolving blocks is to recognize how a completely different solution, one that is not blocked, can achieve the stated goals.

Stay tuned for Part 2 where we share what actually happened in 2017 and Part 3 where we lay out the 2018 plan, which has us coming full circle in our quest to find the right controller board for Holoseat.

The post There and Back Again: An OSHW Project’s Tale – Part 1 appeared first on Model B.

The year is flying by. Sprint 2 is done and suddenly it is time to get everything ready for SyndCon 2017. Our last sprint was a roller coaster ride, full of mission critical Product Backlog Items (PBIs). On numerous occasions we asked ourselves “are going to get enough done before this year’s SyndCon?”  Fortunately, we applied all of the lessons learned from previous sprints and delivered exactly what we needed to lock in the v0.4 design. And I am happy to report we are ready to share our progress with our fellow guild members in August.

How We Did Last Sprint

Review

As we shared in our last sprint kick off post, the number one priority for Sprint 2 was to implement the HID keyboard interface through an Arduino based board. We worked hard in planning to ensure we would be successful. One key to our planning was breaking this PBI down into smaller bites.  Thanks to the smaller PBIs we made slow, steady progress.  We also more quickly identified when and where things were not working. Thanks to this planning, we have fully demonstrated the architecture and implementation we will be using for the v0.4 HID keyboard.

It is worth noting another key to this success was our willingness to adapt our implementation to suit the technology stacks the rest of the CHIP Pro community is adopting. It turns out our initial implementation plan had some hits and misses. For example, we correctly identified Docker as a useful technology for the CHIP Pro, but it is lacking in key documentation. On the other hand, our initial decision to go with Node.js was not sustainable. There is just not enough community support for the combined CHIP/CHIP Pro platform for Node.js related projects. So, we have moved to the language of CHIP IoT development, Python, for the v0.4 firmware.

Retrospective

Overall we had a very good sprint. We accomplished what we needed and demonstrated an improved level of teamwork. That does not mean the sprint was without its challenges. Both Bryan and I had outside blocks at the same time due to work and family demands. This led to our missing several stand up meetings in a row mid-sprint. And, despite how well the sprint ended, the implementation details for the HID keyboard interface looked like they would not be completed as late as week 6 of 8.

Yet, as we noted in our retrospective meeting the theme of Sprint 2 was recovery. Unlike past sprints, we recognized the pattern of missed stand up meetings and immediately resumed meeting. Further, our improved teamwork helped us identify the sticking points around the HID keyboard research.  We were then able to select the proper path forward, leading to a surge in productivity the last two weeks and the successful completion of the sprint.

Bryan and I also identified a new lesson at the close of Sprint 2. The two of us have reached the limit on how much work we can take on in any given sprint. If we want (or need) to take on more work than we have been doing, we must bring in outside resources. These outside resources can include volunteers or contractors.

What We Are Doing This Sprint

The Sprint 3 plan can be summed up in one word, SyndCon. Every PBI is directly related to getting ready to demo and present our progress toward v0.4 at SyndCon. This includes:

• implementing the new sensors we have selected
• upgrading our demo hardware to showcase improved sensitivity and packaging
• creating a professional, scripted demo process (complete with signage and dedicated demonstration games)
• bringing Holoseat swag to give out at SyndCon
• creating our presentations for SyndCon

In case this looks like a lot of work for 7 weeks (yes we are running a truncated sprint), that is because it is. Based on our final lesson from Sprint 2, the Sprint 3 plan includes calling on outside resources to help us get the job done. And, the good news is they have all accepted.  You can see the full list of PBIs on our Sprint 3 plan (click the Sprint 3 tab) and our complete backlog (click the Backlog tab) in our 2017 planning document.

As always, be sure to sign up for our newsletter to keep up on all things Holoseat.  And you can follow the week to week details of this, and future sprints, on the Holoseat project News page (Atom feed).

The post 2017 Sprint 3 Kickoff – Prep for SyndCon 2017 appeared first on Model B.