News

Holoseat: PY18 Sprint 1A Stand Up 2

Added by J. Simmons 14 days ago

J's Report

  • Did
    • V04-51: Implement Serial Monitor feature - implemented unified app infrastructure and completed the synchronous mode for the serial monitor (you can now send messages and observe the direct replies to your messages)
    • V04-14: Select tone ring based on ease to adapt, costs, identical or faster response times, improved single step - printed v3 of the 2 piece tone ring on my printer (it is looking good), made initial contact with TechShop about injection molding and high end 3D printing reviews, took injection mold machine operation class at TechShop, and heard about an injection mold company to look into (Proto Labs)
    • V04-15: Adapt test rig to use the new auto-adjusting cadence firmware - (not on sprint!) Ordered some components and started re-architecting the test rig into a test stand to support all testing/development work (going to want to verify tone rings soon, so we will want the test stand early)
  • Will do
    • V04-51: Implement Serial Monitor feature - begin work on async mode for serial monitor (observe all communications between Holoseat controller and the REST API)
    • V04-14: Select tone ring based on ease to adapt... - Research Proto Labs and follow up with TechShop contacts about review for tone ring
  • Blocked?
    • Work travel coming up, so can only make headway for the next few days

Bryan's Report

  • Did
    • SME-01: Get Jazmint signed up for Lastpass so we can share passwords securely for social media - pinged Jazmint, have not heard back yet
    • SME-02: Split social media accounts out into a separate folder - done
    • SME-03: share only the social media folder with Jazmint - done
    • V04-29: Design a housing in Fusion 360 for the Feather and daughter board as well as the LED button and TRRS jack (Controller Housing) - handed in progress controller prototype to volunteer to start working on controller housing design
    • V04-59: Design scheme for checking the hardware version so the software can find compatibility - done (see discord chat and later docs in wiki)
    • V04-14: Select tone ring based on ease to adapt, ... - got v3 of tone ring design from volunteer to J
    • Other branding work while we have volunteer available - had some early discussions about other branding PBIs with volunteer
    • Sent status email to alpha testers
  • Will do
    • V04-26: Assemble a test Wings to verify design (on proto-wing) - will finish soldering down all components so we have a test unit
    • SME-01: Get Jazmint signed up for Lastpass so we can share passwords securely for social media - follow up with Jazz
    • Write blog post
    • Mail parts to J
    • RAT-12: Ask legal aid about collecting health data and verify requirements for data security - follow up with legal aid
  • Blocked?
    • work travel and house guests after

Joint Work

  • Add trade mark related PBIs to backlog
  • Review and finalize the v0.4 BoM
  • Decide on pin out for hw version number resistors

Holoseat: PY18 Sprint 1A Stand Up 1

Added by J. Simmons 21 days ago

J's Report

  • Did
    • Posted sprint plan to Holoseat news channel
    • RAT-12: Ask legal aid about collecting health data and verify requirements for data security
      • Looked into DC legal aid (it was a bust)
      • Organized questions for legal aid
    • PIC-01: Submit application to Crowd Supply to see if they would be interested in Holoseat
      • Researched application for CrowdSupply (discovered, again, we need a price point for the application)
      • Prepared a Google Doc to capture answers to CrowdSupply application
    • V04-51: Implement Serial Monitor feature
      • Designed common elements for Holoseat app (enable button, profile selector, and cadence display)
      • Designed Serial Monitor UI
      • Started implementing Serial Monitor UI
      • Implemented REST API framework
      • Implemented first few REST API methods (and their counterparts in HSP)
    • V04-49: Implement python serial library for accessing new version of HSP
      • Replaced old manual string parsing code in firmware with Arduino JSON library
      • Developed first draft of Holoseat serial library (nearly feature complete, need to discuss versioning scheme to finalize board checks)
    • V04-14: Select tone ring based on ease to adapt, costs, identical or faster response times, improved single step
      • Provided feedback and test prints for tone ring development
  • Will do
    • V04-51: Implement Serial Monitor feature - Finish implementing Serial Monitor
    • V04-14: Select tone ring based on ease to adapt, costs, identical or faster response times, improved single step - Continue supporting tone ring development (including review about injection molding and printing on TechShop 3D printer)
  • Blocked?
    • no

Bryan's Report

  • Did
    • V04-26: Assemble a test Wings to verify design (on proto-wing) - partially assembled test wing, focused on layout this week
    • V04-71: Branding on keycap - done and key caps ordered
    • V04-59: Design scheme for checking the hardware version so the software can find compatibility - discussed hardware versioning with volunteer
    • V04-14: Select tone ring based on ease to adapt, costs, identical or faster response times, improved single step
      • Worked with volunteer on design
      • ordered magnets
  • Will do
    • SME-01: Get Jazmint signed up for Lastpass so we can share passwors securely for social media
    • SME-02: Split social media accounts out into a seperate folder
    • SME-03: share only the social media folder with Jazmint
    • V04-26: Assemble a test Wings to verify design (on proto-wing)
    • V04-59: Design scheme for checking the hardware version so the software can find compatibility
    • V04-14: Select tone ring based on ease to adapt, costs, identical or faster response times, improved single step
    • Other branding work while we have volunteer available
    • Write a blog post and/or a message to alpha testers
  • Blocked?
    • traveling for work

Holoseat: PY18 Sprint 1A Plan

Added by J. Simmons 27 days ago

The first iteration of Planning Year 2018 (PY18) is over. While we accomplished many key tasks, I hesitate to call it a sprint (we never got to setting up a complete sprint plan). It was more of a kanban run straight off of the evolving backlog. To say it was less than a perfect process is an understatement (you can see all the details in our Review and Retrospective).

We have since finished grooming the PY18 backlog and we have looked at how moving to our new planning year cycle (SyndCon to SyndCon) impacts our annual cadence. Based on this meta-planning work, we are calling the upcoming sprint Sprint 1A (this will put the rest of PY18 in sync with our proposed annual cadence). See below for all of the PY18 Sprint 1A details.

Duration: 6 weeks
Stand Ups: Thursday nights
Start: Oct 26, 2017
End: Dec 7, 2017

Backlog and Full Sprint Plan (see Backlog and Sprint 1A tabs)

User Stories Under Development
  • As a manufacturer I want to source a manufactured tone ring so that I can reduce costs
  • As a developer I want to design a "Wing" so that I can reduce risk to expensive components
  • As a designer I want to source components so I can keep costs low
  • As a designer I want to test components so that I can validate design
  • As a designer I want to develop a housings so that I can avoid having lose electronics sitting on the equipment
  • As a testing coordinator I want to evaulate the design so that I can avoid additional expenses from updates
  • As a developer I want to update the Holoseat Serial Protocol so that I can adjust Holoseat on the fly again
  • As a developer I want to build the desktop app so that I can offer an API to games to directly interact
  • As a developer I want to recreate the Arduino Serial Monitor as a desktop app feature so that I can validate the desktop app architecture
  • As a marketer I want to make sure that the Holoseat logo and images are on the product so that I can promote the brand
  • As a business owner I want to verify requirements for collecting health data so that I can avoid endangering the company
  • As a designer I want to make sure the sensor housing will only need minor adjustments for injection molding so that I can minimize changes between alpha and final
  • As a designer I want to make sure the controller housing will only need minor adjustments for injection molding so that I can minimize changes between alpha and final
  • As a community leader I want to share posts about gamefying vs exerfying so that I can get people to think about things the holoseat way (clarifying the difference)
  • As a product manager I want to share access to social media accounts with Jazz so that she can help with social media
  • As a marketer I want to continue publishing blog posts once a month (on a consistent schedule) so that I have original content to share
  • As a social media consultant I want to educate myself on gamify and exerfy so that I can write better
  • As a business owner I want to research site support for manufacturing process so that I can fill in gaps in organization knowledge and experience
Pre-Sprint Commitments
  • J
    • RAT-12: Ask legal aid about collecting health data and verify requirements for data security
    • V04-49: Implement python serial library for accessing new version of HSP
    • V04-51: Implement Serial Monitor feature
    • PIC-01: Submit application to Crowd Supply to see if they would be interested in Holoseat
  • Bryan
    • V04-26: Assemble a test Wings to verify design (on proto-wing)
    • V04-59: Design scheme for checking the hardware version so the software can find compatibility
    • V04-71: Branding on keycap
    • V04-14: Select tone ring based on ease to adapt, costs, identical or faster response times, improved single step
    • SME-01: Get Jazmint signed up for Lastpass so we can share passwors securely for social media
    • SME-02: Split social media accounts out into a seperate folder
    • SME-03: share only the social media folder with Jazmint

Holoseat: PY18 Sprint 1 Review and Retrospective

Added by J. Simmons 28 days ago

Review

Claiming Done

  • V04-01: Get all testers signed up for the testing resources
  • V04-02: Go over testing resources with testers to confirm all questions or concerns are answered
  • V04-08: Keep meeting info updated on Meeting_Planning channel
  • V04-03: Get all testers to talk on Discord server
  • V04-10: Contact manufacturers to find a few tone rings that may work for us
  • V04-18: Test TRRS mini stereo jacks and cable to confirm ability to replace the network cable based system
  • V04-19: Select new button that should be a drop in replacement that is a through-pin design and screws on from outside of case (or not at all)
  • V04-20: Test new button to confirm it is a drop in replacement
  • V04-21: Decide what components we want to be on the wing
  • V04-42: Develop static mock up of app UI
  • V04-43: Demo pystray library
  • V04-44: Demo pywebview
  • V04-45: Demo flask app development
  • V04-46: Demo serial messaging library suitable for Serial Monitor
  • V04-53: Research how to leverage USB PID
  • V04-54: Follow instructions for registering USB PID with PID codes - http://pid.codes/howto/

Not Claiming Done

  • n/a (sprint was not completely planned)

Retrospective

What went well?

  • The hardware testing
  • Initial work on the new desktop app
  • Getting testers through initial on boarding
  • Got done about the right set of work at about the right time (especially considering we had no formal sprint plan)

What did not go well?

  • No formal sprint plan - What's a sprint plan?
  • Hit the resource bottleneck again because we did not leverage outside resources (direct result of not having a formal sprint plan)
  • The timing for annual planning and needing to get things rolling for the planning year was off
  • Missed some stand ups (old habit coming back to haunt us) due to travel and other outside blocks
  • Travel in general
  • While we got a couple of blog posts got up, the social media continued to stagnate (related to resource constraints)

What can we do better?

  • We need to address annual planning; everything else that did not go well stems from not completing annual planning
    • In the rush to try to have delivery of alpha units by end of year, we cut annual planning short; last planning cycle took 3-4 weeks for planning
    • Need to determine correct annual cadence for planning years running SyndCon to SyndCon
    • Let's lay out the assumptions for our planning year
      • Year runs Sept to Aug
      • Aug is just for SyndCon and recovery from SyndCon
      • Planning year is broken into thirds which are ~2 sprints long each
      • Sept is dedicated to planning (no development)
    • Annual Cadence
      • Third 1
        • Sep: Planning
        • Oct - Nov: Sprint 1
        • Dec: Basically off (any development is out of cycle)
      • Third 2
        • Jan - Feb: Sprint 2
        • Mar - Apr: Sprint 3
      • Third 3
        • May - Jun: Sprint 4
        • Jul - Aug: Sprint 5 (runs short to meet deadline for SyndCon; it is always dedicated to convention prep)
  • We need to discuss how to apply this cadence through the end of calendar year 2017

Holoseat: PY18 Sprint 1 Stand Up 7

Added by J. Simmons 28 days ago

J's Report

  • Did
    • Backlog grooming
    • Laid out the app source code structure in svn
    • Started to re-implement UI layout (running in Flask) - have NavBar done, GUI init code setup for running GUI in its own thread, have empty pages ready for all key functions, have command for posting the GUI URL so users can load GUI up on their phones/tablets if they want
    • Continued multi-threading in Python training
    • Replied back to 6' - no response
    • Replied back to DC Biz Dev Center - no response
    • Researched USB PIDs - see wiki
    • Secured 0xB058 (reference to Model B and our OSHWA cert # US000058) as PID for Holoseat
  • Will do
    • n/a
  • Blocked?
    • no

Bryan's Report

  • Did
    • Backlog grooming
    • Tested bread board build with a tone ring - it worked great!
    • Followed up with Star - no response
    • Ordered updated pins
    • Worked volunteer on updates to tone ring for injection molding/manufacturing in general
  • Will do
    • n/a
  • Blocked?
    • no

Holoseat: PY18 Sprint 1 Stand Up 6

Added by J. Simmons about 1 month ago

J's Report

  • Did
    • Reviewed schematics updates for Bryan
    • Training on Bootstrap for visual layout of app, Python Requests for interaction between GUI and REST API, and started training in multi-threading in Python
    • Developed color scheme for the app UI
  • Will do
    • Backlog grooming
    • Lay out the app source code structure in svn
    • Re-implement UI layout (running in Flask)
    • Continue multi-threading in Python training
    • Reply back to 6' (turn of the year is fine/discuss sending alpha instead of v0.3.5)
    • Follow up with biz dev center
  • Blocked?
    • need the backlog groomed

Bryan's Report

  • Did
    • Completed first bread board build of v0.4, need to test with a tone ring
    • Tried to reach the missing tester
  • Will do
    • Backlog grooming
    • Test bread board build with a tone ring
    • Follow up with Star
  • Blocked?
    • need the backlog groomed **

Holoseat: PY18 Sprint 1 Stand Up 5 (belated)

Added by J. Simmons about 1 month ago

J's Report

  • Did
    • Attended pre-counseling phone call with DC Small Business Dev Center
    • Punted on Oct 6' trip (need to discuss this topic more with Bryan)
    • Tested Flask
    • Tested serial comms with Tornado
    • Got SyndCon post reviewed and posted
    • Created first draft of REST API to wrap the Holoseat Serial Protocol
  • Will do
    • Review schematics updates for Bryan
    • Training on Bootstrap for visual layout of app
  • Blocked?
    • Work travel basically makes this week unusable for Holoseat work

Bryan's Report

  • Did
    • initial solder work for breadboarding
    • Called tester we’ve not heard from
    • started breadboarding
  • Will do
    • Finish breadboarding
    • Update circuit diagram again
    • See about layout on the Feather Proto wing if it works
  • Blocked?
    • more travel

Holoseat: PY18 Sprint 1 Stand Up 4

Added by J. Simmons about 1 month ago

J's Report

  • Did
    • Almost wrapped up meeting scheduling with 6'
    • Tested pystray
    • Completed mockup
    • Drafted SyndCon 2017 Blog Post
    • Looked at access to FB holoseat page - need personal account to register for business management access
  • Will do
    • Attend pre-counseling phone call with DC Small Business Dev Center
    • Wrap up meeting scheduling with 6' crosses fingers
    • Test Flask
    • Start testing serial data link with Tornado
    • Prep for 6' trip
    • Get SyndCon post reviewed by Dragons
  • Blocked?
    • Work travel next week
    • Waiting final confirmation from 6'
    • Got stood up by DC Small Business Dev Center

Bryan's Report

  • Did
    • nothing this week
  • Will do
    • Continue to ping last tester that’s MIA
    • Redo circuit layout based on new breakouts and cables
    • Start building new version on protoboard
  • Blocked?
    • Have been sick and getting caught up at work
    • More travel coming up

Joint Work

  • Backlog grooming

Holoseat: PY18 Sprint 1 Stand Up 3

Added by J. Simmons about 1 month ago

J's Report

  • Did
    • Published Part 1 of 2017 Recap/2018 Plan blog series
    • Registered with and scheduled pre-counseling phone call with DC Small Business Dev Center
    • Updated Holoseat transport box
    • Made significant progress scheduling meeting(s) with 6'
  • Will do
    • Attend pre-counseling phone call with DC Small Business Dev Center
    • Wrap up meeting scheduling with 6' crosses fingers
    • Complete mockup
    • Test pystray
    • Draft SyndCon 2017 Blog Post
    • Address access to FB holoseat page
  • Blocked
    • Things are starting to get back to normal, but we will have to see how it goes

Bryan's Report

  • Did
    • Contacted additional Holoseat testers to get them signed up for resources
    • Worked with vendor over speed wheel, unfortunately they are likely not a option
    • Developed outline for blog post
  • Will do
    • Continue to ping last tester that’s MIA
    • Redo circuit layout based on new breakouts and cables
    • Build new version on protoboard
  • Blocked
    • continued personal travel/time off
    • getting caught up after personal travel/time off

Holoseat: PY18 Sprint 1 Stand Up 2

Added by J. Simmons 2 months ago

Just a couple of quick notes about the next round of sprints:

  • We are moving our planning year to run September to August, identified by the year of the next SyndCon we will present at (e.g Planning Year 2018 or PY18)
  • PY18 planning is still under way, so we are running Sprint 1 a little more ad hoc than normal, so we don't have a full sprint plan to work against yet (we do have the beginnings of a backlog we are working off of)

J's Report

  • Did
    • nothing sighs
  • Will do
    • move my 1st blog post to wp
    • Schedule meeting with DC Small Business Dev Center
    • Update Holoseat transport box
    • Schedule meeting with 6'
  • Will try to get to
    • complete mockup
    • test pystray
    • draft 2nd blog post
    • address access to FB holoseat page
  • Blocks?
    • life and work (as demonstrated by lack of progress this week)

Bryan's Report

  • Did
    • Continued to work with alpha testers to get them signed up on comms channels
    • got all of the parts ordered and they have all come in
    • ordered adhesive samples
    • moved social medial account management moved around per plan
    • set up company structure for FB page
    • contacted a speed wheel vendor
  • Will do
    • continue reaching out to alpha testers
    • continue discussions with speed wheel vendor
    • outline/draft several blog articles
  • Blocks?
    • personal travel/time off

1 2 3 ... 9 Next »

Also available in: Atom