Although the Agile Manifesto was written to guide software development, product development teams can reap great benefits by applying the foundational aspects of Agile to hardware development.
You’ve convinced the powers-that-be that your company should use Model-based Systems Engineering. You’ve done an extensive trade study and picked the tool that you want to use. You’ve completed the budget and IT hurdles to put the tool into the hands of all your engineers. Now what? How does this new tool fit into your product development process? How do you capture your project’s data in the tool? Which diagrams should you use? How do you create your regulatory submission documentation?
These days it seems like everything is becoming a “smart” device. Even the batteries that power smart devices are becoming “smart.” A conventional battery simply exposes positive and return terminals. You’re left to figure out how to use the battery. In contrast, a smart battery looks after itself, tells you what its status is, and even lets you control what it’s doing. Sounds great, doesn’t it? But do you really need a smart battery? And if you do need a smart battery, what’s actually involved in making one?
What were your team members doing a year ago? Did they do brilliant work? Was there room for improvement? Do they even remember the details of what they were working on a year ago? If you’re a fast-paced and dynamic workplace like Syncroness a year may be multiple projects and multiple teams of coworkers ago. Providing feedback and setting goals once a year during an annual review, on a timescale far removed from the timescale of the work being done, can be less than ideal.
Syncroness, Inc., a recognized engineering leader based in Colorado, today was ranked as No. 116 in the Top 250 Private Companies in Colorado by ColoradoBiz Magazine, as measured by revenue growth. This is the fifth year Syncroness has been honored on the top private companies list in Colorado.
Automated unit testing is considered a key practice for delivering quality software in many software development circles. But it’s a practice that’s been slow to gain traction in the embedded software space. That slow uptake is partly due to the unique challenges of writing software that may be tightly bound to the underlying hardware, and partly due to the lack of unit testing tools aimed at the C programming language most commonly used for embedded development.
The Syncroness Community Outreach Committee encourages employees to give back to the community. We volunteer with Habitat for Humanity, Food Bank of the Rockies, Bonfils Blood Drives, National MS Society, Hope House, Boy Scouts of America, Boulder Community Hospital, George Karl Foundation, the Leukemia and Lymphoma Society, and Children’s Hospital Colorado.
To me, Agile most importantly means continuous delivery. When working on a product (software or otherwise) we want to deliver the product in increments, each with more features than the last. We don’t wait for the project to be “done” to deliver…
Agile methods are hugely successful for building software and are being used to develop hardware. But what happens when you need to move beyond 3D printing and Arduino? How do you make smart choices for the future while maintaining your agility?
The National Academy of Sciences, Engineering, and Medicine released the NASA Space Technology Roadmaps and Priorities Revisited report this week summarizing the independent review of NASA’s 14 recently revised technology roadmaps. The committee that performed the review was co-chaired by Syncroness Vice President of Engineering, Todd Mosher, Ph.D. and is the culmination of a year of analysis and formulation of a methodology for future independent reviews.