A Tech Lead’s New Project Checklist

&quot;Understand the importance of the Trinity of delivery: Delivery manager, product owner, tech lead&quot;<p>I&#x27;m only familiar with teams too small to have separate roles like this. How does good software planning scale down to smaller teams -- say 5 or 10 people in the whole organization? Ultimately someone has to be responsible for the same concerns, but I wonder how it maps.<p>In general I&#x27;d love to see a comparison of software teams at different sizes. What are the key, identified roles in a company of 5, 50, or 500? What are habits that smaller organizations ought to borrow from larger ones?

<i>What’s the budget and the value proposition?</i> should be #1. Projects without a clear purpose (happens way more than you might think) are sinking ships you&#x27;ve got to get away from.

Might want to add company size and team size(s). Many of these points show it is most likely for small to medium sized companies. For an enterprise the checklist does not entirely hold due to more specialized roles. Though there are some good tips.

Ask about approved licenses and also make sure you know what you&#x27;ve purchased when it comes to platform service levels.

How about fuck this paradigm?<p>Scrum = Shite verbosity about agile process and training for mgmt larva. Agile = Hyperbole. AWS = I don&#x27;t know better and my developers are &lt; 35 years old or on the make (+ stock). My customers are just stupid. Security = big $$, modest skills, certs for the neglected comptia and northcut industures. I&#x27;m a CEH!! So is every script kiddie on the internet. tester: can&#x27;t write working code, useless to the degree that you come in when they need you to justify junit crap numbers you generated when drunk. This will scale if 12 coors == 12 saudi virgins. analyst: I&#x27;m an experienced tester. tech lead: best resume and best bully of the bunch. I can understand stack exchange! QA: I like your doxygen docs and the test numbers but I have a problem with connecting to server(x) at ip(x) from greenland at 2pm on a sunday. Any ideas? team: Bunch of backstabbing co-moderators.

Here is the other one from today. I should turn this in to an app-style application for employers&#x2F;recruiters to fill out before they contact me. <a href="https:&#x2F;&#x2F;www.sideprojectchecklist.com&#x2F;marketing-checklist&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.sideprojectchecklist.com&#x2F;marketing-checklist&#x2F;</a>

My primary requirement is a demonstration that the site can be torn down and recovered any time – you never know when you will have a DNS problem or someone take over your domain

Unrelated minor rant: Pocket is hopeless when dealing with bullet points. It so often skips list items, especially if they have links in them. I understand that they are trying to avoid including navigation stuff, but overzealous way too often.<p>I wish I could integrate Instapaper with my Kobo ereader instead.

here is what i usually do:<p>-identify weak people in the team with a stinky attitude, those who dont learn and are toxic, do your best to get rid of them.<p>-next identify those mediocre people doing 9-5, maximise their output during those hours, don&#x27;t give them no slack.<p>-finally identify your super stars, cherish them, buy them coffee&#x2F;lunch and give them a lot of slack.<p>for this is a meritocracy, no damn Disneyland.