![]() Initial merge of existing employee information into Active Directory.This idea correlated to the judging criteria and fit well with our team members’ skill sets (and administrative AD permissions!). We could achieve this product result by scripting a merge of employee information from several disparate data sources into our Active Directory. Finally, we aligned on a top choice: making it possible for our new Microsoft Teams app to display organizational diagrams, like this: The team iterated on the feasibility and strength of each product idea – eliminating the weakest product candidates each iteration. During two brainstorming sessions we generated 10 quality ideas for Hackathon projects. In the first hour of Hackathon, I virtually gathered my team – meeting some of the newer employees for the first time. That’s why it’s so important to have a semi-structured approach to choosing and refining your Hackathon idea. Leading a Hackathon team of people who might not know each other, or have different levels of engineering experience, has unique challenges. 2020 Bonus Category: Helps form connections between teams.Applicability to Logicworks: how it helps Logicworks employees or clients perform smarter.Execution: quality of the work performed during hackathon.Teams have 24-hours to create something and then 5 minutes to present their creation to judges, who award points based on these criteria: The Hackathon teams are judged by any interested employees at Logicworks. My team also included our Chief Information Security Officer, our IT Systems Admin, a database architect, and a summer intern. Logicworks generously offered an extra vacation day to anyone participating in the Hackathon!įour of the Hackathon teams were created in this ad-hoc way (the other teams were more traditional pre-formed groups of software developers that wished to create something together).Īs an example, I led one of these ad-hoc teams.These ad-hoc teams were led by product managers – more on that below. Instead, these four ad-hoc Hackathon teams were comprised of employees across divisions and geographies – many of whom had never met before. To encourage future cross-team collaboration, Logicworks purposefully separated individuals that already routinely work with each other.The product manager was tasked with driving a product execution process that made best use of the talents on their team. These participants were then placed on ad-hoc teams led by a product manager. ![]() Logicworks encouraged employees without teams to sign up.Logicworks’ leadership team made three key changes to encourage more participation from semi-technical and non-technical employees from across the company – employees that might not typically join a Hackathon. In past Hackathons, the most common participants were pre-formed teams of software developers. If you’re planning on hosting a Hackathon at your company, here are a few tips – and some highlights from our Hackathon – that we hope help you bring team members together. But it was also an important opportunity to encourage collaboration across teams and departments, especially during these isolating times. Obviously, this year’s Hackathon was a bit different: all teams were remote and had to collaborate virtually. Last week, we wrapped up our annual Logicworks Hackathon. By Daniel Pohl, Director of Product Management
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |