Reflections on the craft and science of managing software projects
While companies rightly spend a lot of time thinking about their business goals and technology choices, they often ignore how best to combine them effectively into a successful software delivery operation. We can all recount being in a software project that failed despite having good ideas and technology choices behind it, leaving everyone miserable in its aftermath: “Is it the team’s fault?.. But didn’t we hire the best? What could have gone wrong?” Join us in this series as we explore such questions and more...
5. Mar 1, Friday: Measuring engineering productivity: Old pitfalls and new approaches - by Sudheer Bandaru
4. Feb 1, Thu: Exploring connections between queueing theory and project management, by Harsha Honnappa
3. Dec 21, Thu: When Quality Matters: Transcending resource barriers during software delivery - by Deepti Agrawal
2. Nov 29, Wed: Software Delivery: Prioritizing and optimizing for impact - by Gaurav Lochan
1. Nov 3, Friday: A bird’s eye view of software project management - a conversation with Ranjan Sakalley
Below is a selective snapshot of some major recent community conversations regarding how software projects are being run:
Pramod Biligiri is founder and CEO at Bitken Technologies. He works as a consultant for data engineering and data infrastructure related projects.
Mayankk Banerjee is a veteran CTO who has led Technology, Operations and Data science teams for global organizations like HelloFresh, Delhivery, Yahoo and Tally. He now spends his time being a fractional-Cxo at OldMonks,tinkering with code and coaching young engineering leaders and founders towards their next level of growth.
This project consists of a series of talks. View the schedule here. If you wish to speak on this forum, leave a comment.
The talks will be held offline and online. RSVP to stay updated.
This series of talks is made possible by contributions from Rootconf members. You can support similar activities by picking up a membership here.
Join the Rootconf Telegram group at https://t.me/rootconf or follow @rootconf on Twitter.
For inquiries, contact Rootconf at +91-7676332020.
Pramod Biligiri
@pramodbiligiri
Gaurav Lochan
@gauravl Editor
Submitted Oct 18, 2023
Date and time: Nov 29, Wed, 9 PM - 9:30 PM IST, followed by 30 min of Q&A
Any startup has more things to do than it has engineering bandwidth for. Yet, a common mistake fast moving teams can make is to pick projects without enough diligence on the potential impact. When the project is delivered, they don’t see the expected impact (or worse, don’t even measure it), theorise why, and then move on to the next project.
One thing I learned at Facebook was to invest time on understanding the problem, identifying levers, calculating the potential impact, and then agreeing on appropriate data to measure impact and progress. And when projects don’t deliver the expected impact, there is even more effort spent to understand why, and potentially iterate (or halt when appropriate).
I’m going to share a few examples and pitfalls, and maybe talk about cupcakes too. This is relevant to EMs as well as ICs, since impact is universally loved 🙂
About the speaker
Gaurav Lochan is a Head of Engineering (and US site lead) for PhonePe, where he manages the app platform team. Prior to that, he worked at Meta and WhatsApp for 8 years on mobile platforms and market specific efforts, at Little Eye Labs, Flipkart, his own Android startup (in 2012), and companies like VMware and Microsoft
About the moderator
Sanchita Agarwal is an engineering leader with more than a decade of experience building mobile first products. In her last role, she was Head of Engineering at Obvious, a digital product consultancy where she led delivery of multiple cross platform projects for products like Swiggy and Slice. Before that, she helped build the Android Partner app at Ola and the Health & Chat apps at Samsung R&D India.
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}