entrepreneurship, Experience, Experiment, Failing, Focus, hackathon, hustle, Improvement, IT, Learning Lessons, Technology, Trying, Zoning

Why Hackathons Are Awesome: Hacking Detroit’s Zoning Code

For the last two months, I participated in a monthly hackathon event called the Detroit Civic Hackathon (next one is November 12!). These were the first two installments of what is becoming a monthly event that originated from a monthly happy hour meet up called The Detroit Urban Tech Meetup.

These past two events were great! The past few days I reflected on why these two hackathons were awesome.

Focus On Your Passion

First, hackathons are awesome because they enable a large amount of dedicated focus. In my day-to-day work, I do not spend more than 2-4 hours focused on something, unless I am working outside of the normal 9-5 business hours – I get interrupted way to often. Hackathon’s are special because they allow you to block out the world and spend deliberate time working on whatever problem you are trying to solve.

In addition, hackathons harness this focus on your passion. For me, I am passionate about learning new technology and cities. In this case, I am learning JavaScript and the React library and trying to understand/solve a problem related to city zoning (more on this soon). This hackathon’s theme is cities, but other hackathons may be more open or have a different theme. Either way, I suggest trying a hackathon that aligns to something you are passionate about.  

Engaging Problem

For these past two hackathons, I was excited to be taking on a problem that was challenging and exciting to me – zoning codes. Zoning is something you may not think about but impacts the way many cities in the US are currently laid out. For example, zoning laws usually prevent a strip club from being built or operating next to a middle school (crude example but I think it makes the example very clear). In general, zoning regulates a city and town’s land use by permitting or prohibiting certain uses based on the zoning codes.

One problem is that most zoning ordinances are not easily accessible. Zoning laws and ordinances can be hundreds of PDF pages long and each zone can be extremely hard and sometimes costly to understand. This is Detroit’s Zoning ordinance – it’s a light read 😜.

Our idea, spearheaded by a guy who was passionate about this topic, is to help make this information easier to access and digest. Our idea is to create basic website that helps take this information out of the PDF and puts it into a more user-friendly web format.

Great People

The last major reason hackathons are awesome is because of the people you meet. Each event I met new and passionate individuals. Some of them are working on this zoning project, others have their own interests and projects. I met a data scientist who works at Ford but is from the Middle East where he used to be banker. I met an MIT graduate who engineered autonomous vehicles for a company that was purchased by Ford. I met a transit advocate who does design work for the Regional Chamber. Lastly, Jimmy, the guy spearheading this idea, works for the city of Detroit. He is a huge city, transit and do the right thing advocate. Also, he is a talented web engineer. It is always great to be surrounded by people that want to do great things and in an area that you are passionate in.

Try One and Check Out Our Project!

These are three reasons I believe hackathons are awesome. I participated in several of them over the years and I love focusing on learning, working on things I am passionate about and meeting great people along the way. I strongly recommend you try a hackathon to see what it is like. If you have similar or different thoughts, let me know! I’d love to hear what you think.

PS – Jimmy made some great updates yesterday and this project is already leaps and bounds exceeding my expectations. Check it out here: Zoning Guide Detroit

Group getting ready for the Inaugural Detroit Civic Hackathon in September 2019

Agile, Agile, Communication, Experience, Experiment, Failing, Focus, Improvement, IT, Leadership, Learning Lessons, Real Estate, Release Train Engineer, SAFe, Scrum, SDLC, Technology, Trying

A New RTE’s Struggles

As a new Release Train Engineer and former Scrum Master, I am ambitious and excited to dive in to help my train and teams succeed. In both roles, I struggle challenging and supporting my trains and teams to follow a few concepts, I believe are valuable.

Vertical Delivery (working software is the primary measure of progress)

Why is this important?

Working software demonstrates progress, enables healthy feedback into the development process without too much re-work and illustrates how much work it takes to deliver amazing software (plus we can celebrate the progress!)

My Struggle

Overall, shifting mindsets is hard. Our tech team can do the work. Moving away from getting everything together from the onset, is the difficult piece. Getting one piece of data from the database to the UI or even faking the data and getting data to flow from one place to the front end can be a big change. One thing I’ve seen that seems to help think through how to deliver vertically – during PI Planning, one team planned out what they would demo at the end of each iteration. If the demo description didn’t seem to deliver new value, the work may not be very vertical.

Set Based Design (assuming variability; preserve options)

Why is this important?

Change is inevitable. This helps designs and solutions pivot away from dead ends when new information is acquired. Also, this helps support innovation and conquer unknowns.

My struggle

From my perspective, during PI Planning or Iteration Planning the team has a clear idea of how they are going to do something and then go and do that thing. While this makes sense (SAFe also mentions how this is normal), it seems like we hurt our ability to innovate and try new solutions that may work better than just sticking to the plan (responding to change > following a plan). I don’t know if this is just a concern because of the technology we use and mindset we’ve created or if every organization has this kind of dilemma when also trying to deliver valuable working software.

Improved Predictability (program execution)

Why is this important?

Predictability helps others understand when they can receive their valuable working software. The more predictable a team, the better experience and experiences matter a lot. For example, if we expect websites to load within milliseconds and it takes 20 seconds to load a website that will result in a bad experience. That experience matters because we won’t go back to that website if it takes a long time to load.

My struggle

Sizing is hard. Sizing is an estimate, but it doesn’t need to be precise. I think this takes practice and the better the work is broken down, which also takes practice, the better we can size. I believe the skill of sizing can be improved and results in better expectations when it comes to major gaps. Often, I see rushed estimations (maybe because of pressure) or I don’t see a lot of time spent thinking through the estimates. Again, there is a delicate balance between wasting time on solving the entire story (analysis paralysis) versus getting just enough information to estimate how long it will take to complete the work.

What do you think?

I know the teams and trains I work with can execute on these concepts. I think as an RTE I can better support them in doing this by finding examples, finding mentors to help guide them and being unafraid to challenge “the why” when someone says it “can’t be done” like that.

I wanted to share my struggles because I think others have these struggles, and it is OK to openly talk about what we are working through. If anyone has any suggestions or thoughts, I’d love to hear from you and what you learned along the way!

Photo Credit: https://medium.com/@media_75624/release-train-engineer-rte-is-not-a-traditional-manager-b51536bd6664

7 Habits, Agile, Agile, Experiment, Focus, Goals, Improvement, IT, Leadership, Learning Lessons, PI Planning, Release Train Engineer, SAFe, Scrum, SDLC, success, Technology, Tools, Trying, Vision

Prioritizing for I & A and PI Planning

A few weeks ago I started a new position called Release Train Engineer(RTE). This role is responsible for facilitating the Agile Release Train (ART) moves efficiently and executes effectively.  

When I started the position in late June, I had 2.5 weeks to get prepared for the two most significant events within the Scaled Agile Framework (SAFe) that fall on the same week – Inspect & Adapt workshop (I&A) and Program Increment (PI) Planning. I & A is the final event during the PI and PI Planning is the kickoff to the next PI. I & A is an opportunity to celebrate all the great work done in the past PI and identify ways to relentlessly improve for the next PI. PI Planning kicks off the next quarter to determine what work can get accomplished within the PI.

I quickly realized with my end goal in mind (a successful I & A and PI Planning) I needed to identify what was the most important (and urgent in this case) things to get done and prioritize those items accordingly. (side note: in the future, I hope to find ways to move some of these items into quadrant 2, so they are less urgent and just as important)

Here is what I did to get ramped up and successfully facilitate I & A and PI Planning

  1. Identify the right people – Making sure I knew who the Product Manager (PM), Product Owners (PO), Scrum Masters (SM), Solution Architect and Software Architect were, was my number one item. This was my top priority because I needed to understand what work was going into the next PI Planning and understand how the current and almost completed PI was coming along. Asking questions to the right people would help me understand the most important information in a short period of time.
  2. Understanding the features being brought into PI Planning – This was my second highest priority because the RTE needs to make sure these items are ready for PI planning. The RTE doesn’t control this work and due to this, they should make sure features are as ready as they can be before PI Planning. If the features are not ready, the RTE needs to facilitate their readiness. In this case, we had a few features intended on being ready for PI planning, but one feature needed to be broken down. The PO and Architects did a great job of working in the last two weeks to get this feature broken down in a way that multiple teams could work together, rather than dumping all the work on one team.
  3. Making sure socialization happens and is helpful – Socialization is hard but important, which is why as a new RTE I wanted to make sure this was happening and going well. Socialization is a proactive preparation approach to PI Planning. If the features aren’t ready or unclear, socialization will suffer because the team will get bogged down by questions and may cause confusion in the future. A lack luster socialization will create inefficiencies in PI Planning, which can slow down a very fast paced two days (you can read my last article here about socialization).
  4. Brainstorming the I & A narrative – I & A is an opportunity to tell a story about the train’s journey during the PI. It is not a time just to dump data or point fingers. It is a time to improve and part of that improvement is to understand the context behind what happened in the PI using data to help elevate the narrative. I chose Grit as the anecdote to tell the story. The team has a ton of passion about Appraisals and persevered through many challenges. The data helped show how a lot of great things were achieved, despite the challenges throughout the PI.   
  5. Understanding data – Data can be dangerous if used incorrectly or misunderstood. As a new RTE who was not part of the train in the past, I was unsure what data was being looked at and measured throughout the PI. I talked with several of the right people (like the Scrum Master) to understand what they were or were not tracking. Also, I bounced ideas off other RTEs to identify what data made sense to use. I used a handful of data points in our I & A: Capacity Allocation – Planned versus Actual, Train Velocity – showing how work from another PI came in throughout the PI, and Cumulative Flow Diagram – showed how our cycle time was pretty good despite lots of unplanned work.
  6. Reviewing the SAFe site – When I started, I had a working knowledge of SAFe and the RTE role, but I am always learning and finding new information. In fact, I referred to the SAFe site on a regular basis when I was a Scrum Master. As I began to prepare my presentation, I constantly referred to SAFe’s site to make sure all my presentations hit on the major items needed for both events.
  7. PowerPoint – Creating my slide decks was really the last thing I did, BUT it took way more time than I anticipated. PowerPoint is not something I use often because I don’t give a ton of presentations and when I do use PowerPoint, I don’t make a bunch of slides. This time around, I knew I needed more information on the slides especially because of the Problem-Solving Workshop. Despite the time I spent working in PowerPoint, I still believe it made sense to prioritize this last because everything else I did before this gave me the content, I needed for my slide deck.

Image credit: https://www.developgoodhabits.com/eisenhower-matrix/

Experience, Experiment, Failing, Goals, Improvement, Leadership, Learning Lessons, Parents Experience, Trying

Growing From Fatherhood

I hope all the dads out there had a great Father’s Day weekend!

Becoming a father is hard to describe. I did a lot to “prepare” for it. I read books, articles, attended classes and talked with other fathers about their experience. I knew this journey would be hard and I knew it would help me grow as a person and as a leader.

Here are four ways I am growing as a new father. For any new fathers, how have you grown?

Patience towards achieving goals like having our daughter sleep in their crib

  • Patience with a newborn is critical. When a baby cries for a while, it can quickly test your mental and physical resolve. Being patient and sticking towards achieving the end goal is really helpful to persevere through the tough times. It’s easy to completely change gears and try soothing techniques that work against your end goals in the long term
  • We wanted our daughter to sleep in her room and in her crib. Early on, we wanted to avoid using sleep props (swings, bouncers, our arms, beds etc) so our daughter would get used to sleeping in the crib and in the room. When she cried, it was really tough to not use a swing or bouncer, but we chose to try and rock her to sleep in our arms and once she was sleepy, put her back in the crib. She currently, sleeps in her room and crib without issue.

Asking for help so you can get much needed sleep

  • Newborns are literally a handful. Being OK to ask for help, is required (and expected!). Asking visiting family or friends to bring over food, help with cleaning up or taking the baby for a bit so new parents can get some much needed sleep, is something I am not always comfortable doing.
  • As a new parent, I’ve learned to be better at asking for help when I think I am hitting a breaking point or I need to accomplish a few overdue things. When my parents were in town to visit, I gave my daughter to my parents for a few hours, so Kayla and I could get some uninterrupted sleep, which was extremely helpful.

Trying, failing (accidentally choking 😬) and learning from experiences like administering medicine

  • Trial and error is a key component to solving various baby related problems. One evening our daughter seemed to have some bad gas. We had some “gas medicine” that we decided to try.
  • I made the mistake of feeding her the medicine to fast and while she was lying flat on her back. This caused her to choke for a few seconds and this event became (still is) the scariest moment of my early fatherhood.
  • I learned from this experience that any medicine should be administered slowly and with the baby at an angle, to help her swallow. Since then, she hasn’t choked and Kayla hasn’t choked me 😀

Setting work boundaries and enjoying the moment because this time is precious

  • Making sure you create the time and space to be present for things that matter most to you is challenging and important. Most people we’ve talked with say the newborn time goes by quickly. Since going back to work and spending a fraction of my day with my daughter, I can see why people say this. I haven’t missed too much yet, one time she rolled front to back and I miss all of her smiles, but I am sure I will miss more.
  • I am creating clearer work boundaries, so I can be home for her two evening feedings. I want to make sure I have the time I want with my daughter and I want to make sure everyone at work understands that you should set boundaries based on what is important to you. For me, this is my growing family. Work can be very fulfilling, but it doesn’t have to be all consuming.
7 Habits, Agile, Estimation, Experience, Improvement, Leadership, Learning Lessons, SAFe, SDLC, Technology, Vision

3 Tips For Your Next PI Planning

April kicked off our second Program Increment (PI) Planning event using the SAFe framework. My team and I reflected on the difference between PI 1 Planning and PI 2 Planning.

Three topics came up that we believe helped us improve our PI Planning.

Clear Socialization Purpose and Different Meeting Types

  • Understanding the purpose of socialization helped the team understand why socialization was so important and what needed to be accomplished during these meetings. This led the team to identify what they already knew and what gaps they needed learn, which led to better questions during each session.
  • Our Product Owner used a variety of socialization meeting types to produce new insights and different questions.
    1. High level, first pass – we just went over the features we intended to plan during PI Planning. This was to get our feet wet.
    2. In depth with shared services – This helped us think about our dependencies and ask questions we didn’t think of during our first session.
    3. Teach Back – Our Development Team taught our Product Owner the features we were going to work one. Any gaps in their teachings our Product Owner answered in order to finalize our preparations for PI Planning.
  • Side note: The teach back was inspired by a separate team that was planning on doing the same thing!

Begin With The End In Mind Strategy Towards Team PI Objectives

  • Identifying and clearly writing our PI objectives upfront helped the team envision our destination, so we spent the majority of time figuring out how to get there.
    1. The Development Team did an excellent job using the remaining time to come up with how to accomplish the objectives and they were able to take on unexpected work because it fit into our destination.
    2. A fourth feature was brought to us and because of our clear objectives, the Development Team knew they could commit to the feature.
  • Working closely with our business stakeholders and other train leaders to get feedback on our objectives helped speed up the process. This prevented us from getting stuck and verified we were headed in the right direction early in the process.
    1. We had great conversations about what should and shouldn’t be a stretch objective.
    2. These conversations helped us think about what we truly control and not trying to achieve outcomes out of our control.

Shorter Feedback Loops From Shared Services and Business Stakeholders

  • Leveraging our shared services with more urgency and without hesitation helped us get answers quickly and prevented major bottlenecks in the planning process
    1. Listening for key phrases like ‘I am not sure how that works’ or ‘I assume that is what was meant’ immediately triggered our Scrum Master to bring in stakeholders, shared services or other leaders to help get answers
  • Working hand-in-hand with business stakeholders helped improve ideas around the objectives to avoid unclear wording and reduced time to get business buy-in when finalizing our objectives.
    1. Also, because we were getting our business stakeholders involved earlier, they seemed more engaged and more part of the team.

What helped you in your PI Planning or what do you think of these tips? Let me know!

Photo Credit: https://www.agileoctane.com/2018/03/31/the-magic-of-safe-pi-planning/

Communication, Discipline, Experience, Improvement, Leadership, Learning Lessons, Remote, Remote Leadership, Self-Awareness, success, Team Building, Technology

After One Year, I Stopped Working Remotely

I spent the past year working remotely. Working remotely sounded great! I envisioned that I’d be able to work from anywhere and be super productive. I talked to other remote team members to try and anticipate any issues and made preparations based on their suggestions. I thought I was prepared. It’s not exactly like the feature image for this post, but I think it can be close. Here are my learning lessons.

What Went Well

I was always caught up on email, rarely late to meetings and always got solo tasks completed on time.

Also, I found that leading remote teams, as a remote team leader, really helped me understand some of the challenges of being remote. I believe it enhanced leading remote team members, more than leading remote team members strictly from an office, as I have done in the past.

What Didn’t Go Well

I found myself struggling to collaborate with my leadership group and other team members at times, I spent a  lot of time making calls and leaving messages, sometimes I was physically uncomfortable and most unexpectedly, I was more lonely than I anticipated.

Bottom Line

Working remotely can definitely work, it just didn’t work for me. I prefer to work in the offices and around other people, rather than work remotely at home.


For me in my current role, my strengths are best suited for in-person interactions and I personally work better when I am in an office. I thought about working from a co-working space, but never took action on that, although I would encourage and suggest co-working spaces to others, if a viable option.

Suggestions For Others

I believe taking time to think about implementing these suggestions can improve and help anyone that is looking to transition into a remote environment. What is your experience? Let me know!

Try It Out Before Making The Jump

Remote work may or may not be for you. You should think about your strengths (more below), talk to other remote team members to understand their insights and try a short period of seriously working from home, before working remotely full time to see what works best for you. I suggest a three month trial period because it’s short enough to get a good understanding if it is right for you but not too long that you may suffer from it. Also, I suggest looking into a co-working space and trying that during your trial period.

Know Thy Self

What are your strengths? What allows you to bring your very best, as often as possible? If you don’t know these, you should spend some time reflecting and identify these items.

For me, my strengths are my physical energy, my curiosity to learn from others and build relationships, and my general energy/enthusiasm on a day-to-day basis. When I moved, I didn’t realize I’d be positioning myself in a way that impacted these. I realize you can still accomplish some of these things over the phone or via Skype/Zoom, but I determined remote work limited these strengths at times.

I Really Missed Office Furniture

Good desk chairs ARE SO WORTH IT! I missed our desk chairs more than any other material object. No free coffee, slushies, snacks, standing desks, fun events etc., will compare to how much a comfortable desk chair will literally make or break your work week. I bought a cheap IKEA desk chair on craigslist and it was fine, for a few weeks. Then it wasn’t. If you are seriously going to work remotely, invest in your office set up or work from a co-working space that has good furniture. A great desk chair, good desk and second monitor are essential, in my opinion, for a baseline level of success as a remote team member.

Working By Yourself Can Be Lonely

I enjoy working around other people that want to do great things. It inspires me and it provides a layer of support that I didn’t realize I needed until I moved.

Working at home, alone, became pretty lonely. I still got my work done, but it was harder to bounce ideas off people and build relationships with people you don’t know as well. I really enjoy bouncing ideas off others, but to be successful (in my opinion) you need to bounce ideas off lots of different people all the time. Building newer relationships to do this, remotely, was a lot more difficult for me than I anticipated.

Working With Non-Remote Team Members Requires Good Technology

This is a really big thing. If you’ve never worked remotely (different than working from home one day a week), it can be really hard to understand how to interact or connect with a remote TM. The amount of meetings where Zoom (remote conference room tech) didn’t work properly, happened multiple times per week.

In addition, make sure you set up expectations with yourself and your team on how you will be communicating on a regular basis. Using Zoom/Skype + a web cam is the best in my opinion because it’s the closest thing to face-to-face communication. It is great to see people, rather than just using a phone.

I did find that calling people from your cell phone in a day where robo-calls makes you feel really popular requires more time leaving messages, sending follow up emails/IMs and then waiting for replies. This became less efficient than I expected at first.

Keep A Routine & Get Some Fresh Air

I would wake up, bike to work, workout, shower, go to the office and eat breakfast in the office. This was my morning routine for most of the time I worked in Detroit. When I moved, I tried a few different things and ultimately found that minus a commute, working out before work, showering and eating breakfast set me up for success before I logged on  for the day.

Just because you work remotely, doesn’t mean you should sacrifice what makes you successful at getting prepared  to bring your best to work. You should prepare yourself just like you were going to the office, minus the commute.

Lastly, now that you aren’t commuting anymore take some time to leave your space and get some fresh air. While I was advised to separate your work space from your living space, I couldn’t do that. If you can’t afford to separate spaces, I believe it’s important to regularly separate yourself from your space so you avoid cabin fever.


Picture credit: https://www.myob.com/au/blog/the-future-of-working-remotely/

entrepreneurship, Flipping, Goals, Hard Money, hustle, Hustle Estate, Improvement, Leadership, Learning Lessons, Purchase, Real Estate, Rehab, success, Technology

Hustle Estate – Flipping Homes 101 – Ep 5

Flipping Homes 101 – Ed and Isaac walk through the overall process it takes to flip a home. Ed talks about where he buys homes from, what to think about when looking to flip a home and how to get a hard money loan.

Feel free to reach out with questions or comments on Twitter/Instagram (@HustleEstate) or send us an email HustleEstate1@gmail.com

Happy hustling!


Music – Showtime by Artlss – https://www.melodyloops.com/tracks/showtime/