Startup Mentality Project Management
I like to start with saying that project management is a continuous improvement in process and management. From stand-up meetings, to aligning one on one cross-dependencies, every small and big details matter. It’s the construction of small details that form the big picture and so recommendation is that it all needs to start small. Most critical is that human habits, communication styles, and level of authenticity plays a big role in meeting milestones. In my 18 years of experience, I have yet to be in a team where project finished on time and with right expectations. That combination is almost impossible perfect, that is why project management are best adaptively programmed to choose progress over perfection. The best outcome is always that project is perfectly delivered, well then kudos as that is always the aim. I wonder how organizations like NASA, Nuclear Power Stations, and other life involving projects feel about perfection. The right management is what works for your mixture of characters placing team members where their strengths brings the best for the project. This is not always easy for many teams due to job titles, and tied up work responsibilities. And, then there is always politics and ego.
FILL THE BUCKETS
It makes sense to fill work buckets as smaller goals and assigned to team members. I like to take this further and fill buckets that cross connect among other members to create “development partnerships”. This type of bucketing creates checks and balances, and build accountability towards the project. Its productive if team is given smaller goals – especially for big projects than run long. Not all the members in the team are going to be visionaries to identify and float up market prevalent gaps. has their bucket filled over smaller goals. This is easy said than done. Filling the bucket is not as easy because it requires product and experience teams to be way ahead of the curve. Often in agile environments, you are not necessarily building requirements for the all interfaces. Sequential flow of requirements into development often does not let you build
Check – “Build the right features”
GIVE SMALL KNOWLEDGE EARLY
What’s to come and start handing of expectations early. Send some materials for team member to individually read up. I usually do not allocate time for this. I just want them to keep in back of their minds, and if there mind wonders one day on this topic, they will research it. Good candidates passionate to move forward, learn and believe in the vision of the project will at least make an attempt. Overtime, you can see and evolve this based on each individual’s personality. Some people like converted this to an assignment, others like this as weekend reading when they are not involved with hard code deliverables. Most effective to deliver this is around Friday morning, where it can not only come handy way if there is any lack of tasks.
Bottom line is that granting small knowledge early needs to be a mindful activity, not just here are some documents or links, please read on your “Spare time”. If you need allocate time for this, do so.