Suggestions
Marc Rössler
IT Interim Manager, Consultant and Agile Coach
Marc Rössler is an experienced IT Leader and CTO with a demonstrated history of working in the computer industry.1 He is currently working as a Management Consultant and Agile Coach at Proscaler.1
Professional Background
Prior to his current role, Marc Rössler was associated with Unicepta, where he gained expertise in digital transformation, transitioning "from project to product," and AI-based automation.3 He left Unicepta in December 2022, expressing gratitude for his time there and excitement about applying his skills to new challenges and contexts.3
Education and Skills
Marc Rössler's educational background includes studies at the University of Duisburg-Essen.1 His professional focus areas appear to include:
- Digital transformation
- Agile methodologies
- AI-based automation
- IT leadership
LinkedIn Presence
Marc Rössler maintains an active presence on LinkedIn, where his profile can be found under the username "marc-roessler".1 It's worth noting that there are multiple professionals named Marc Rössler on LinkedIn, with at least 10 profiles sharing this name.2
Highlights
TL;DR - How does DevEx relate to engineering productivity and does it matter?
Developer Experience, or short DevEx describes how easy or difficult it is for a developer to perform essential tasks needed to implement a software change. Poor DevEx could be due to incomplete requirements, missing feedback, constant interruptions, or undocumented hard to read code.
Why Does DevEx Matter? Consider DevEx as a well-organized toolbox. When developers have a positive experience, they work more effectively. Research from the DORA group shows that practices supporting good DevEx correlate with improved economic results. So, it’s not just about code; it’s about creating valuable outcomes.
Is DevEx the same as productivity? The framing of productivity for software development as DevEx focusing on one aspect of productivity and is driven by marketing attempts to sell tooling to measure or improve the developer experience. Still, there is value in this concept: As leaders, we must recognize that designing the work environment for our software teams significantly impacts their productivity. Monitoring and optimizing DevEx is a top priority.
Getting Started with DevEx: Practical Steps 1️⃣ Deep Work Time: Ensure your developers have uninterrupted blocks of time for focused work. Minimize distractions, including meetings and constant interruptions. 2️⃣ Simplify Tools and Processes: Seek easy wins by streamlining tools and processes. Unnecessary complexity drains cognitive capacity. 3️⃣ Measure and Manage Engineering Productivity: Whether you invest in DevEx enhancements, wield AI tools, or architect optimized solutions, measurement is your compass. Without it, assessing impact becomes a foggy quest.
🔥 What is Your Take and Experience on DevEx and Productivity? 🙌
5 Essential Questions to Ask Before Measuring Engineering Productivity
Whether you're intrigued by the 2023 cage fight between McKinsey and leading agile thinkers on engineering productivity, or simply interested in the topic, the “The Pragmatic Engineer” substack offers an excellent edition featuring insights into how other companies approach productivity metrics (find the link in the comments).
Additionally, I've put together 5 key questions to guide you in approaching the measurement of engineering productivity:
1️⃣ Did you start with the WHY? Define what you aim to achieve with "measuring engineering productivity".
If your goal is to "pressure the engineering team," there are simpler ways. If you're looking to benchmark suppliers or teams, maybe yes, maybe no. However, if your objective is to establish a metric-based feedback system to encourage continuous improvement, you're on the right track! Still, spend time on refining your aspiration. It will help you to keep the right focus.
2️⃣ Can you acknowledge that there's no single, straightforward metric for software engineering productivity?
Stay away from oversimplified metrics such as Lines of Code or Story Points, as this will negatively impact your productivity.
3️⃣ Are you aware that this isn't applicable for individual engineer performance reviews?
Productivity can only be gauged at a team, unit, or company-wide level. While each engineer contributes to productivity, it's primarily the task of Engineering Managers, Directors, and the CTO to enhance it. Therefore, consider using these metrics for their performance reviews.
4️⃣ Are you aware that this is not solely a “managerial” task, but requires alignment with the entire team?
Without involvement, your team will be concerned about being "monitored" by a system they don't comprehend. Moreover, you won't harness the power of focus and alignment that stems from clarity on (1) what's important and (2) how it's measured.
5️⃣ Does your team possess a metric-driven mindset, or are you prepared to foster one?
Metrics, as utilized in KPIs and OKRs, are powerful tools for alignment and focus, but they necessitate a metric-driven mindset. You'll notice the lack of such a mindset through absent or unmanaged KPIs and OKRs, and an emphasis on activity and “busyness” reporting instead of tracking progress towards defined and aligned outcomes.
If you've read this far, it's evident that you're serious about measuring engineering productivity - and for good reason. It will not only enhance focus and improve your team's productivity, but also navigate challenges like economic downturns, shortage of skilled workers and the opportunities of AI-powered programming.
What has been your experience or perspective on measuring engineering productivity? How do you perceive the measurement approaches used by other tech companies? I'd love to hear your thoughts.
