Should a project manager push developers to work more hours due to mistakes of manager schedule setting?
Last updated: October 11, 2022 Read in fullscreen view
Recommended for you
- 01 Aug 2024
The Standish Group report 83.9% of IT projects partially or completely fail 444/2214 - 13 Apr 2024 Lessons on Teamwork and Leadership from Chinese story book "Journey to the West" 112/1161
- 02 Nov 2021 What is Terms of Reference (ToR)? 78/1631
- 18 Oct 2020 How to use the "Knowns" and "Unknowns" technique to manage assumptions 66/1146
- 03 Apr 2022 Microsoft Solutions Framework (MSF) 57/1347
- 13 Dec 2020 Move fast, fail fast, fail-safe 48/359
- 06 Feb 2021 Why fail fast and learn fast? 47/503
- 01 Oct 2020 Fail fast, learn faster with Agile methodology 47/1090
- 03 Jan 2023 Organizing your agile teams? Think about M.A.T (Mastery, Autonomy, Purpose) 42/421
- 14 Oct 2021 Advantages and Disadvantages of Time and Material Contract (T&M) 41/908
- 12 Aug 2022 What is End-to-end project management? 39/493
- 18 Aug 2022 What are the consequences of poor requirements with software development projects? 37/294
- 02 May 2022 What Is RAID in Project Management? (With Pros and Cons) 36/857
- 23 Jun 2024 Best Practices for Managing Project Escalations 36/237
- 18 Dec 2023 The Cone of Uncertainty in Scrum & Requirement Definition 36/740
- 07 Jul 2022 Managing Project Execution Terms 34/440
- 08 Oct 2022 KPI - The New Leadership 34/629
- 10 Apr 2024 The Parking Lot Method: Unlocking a Simple Secret to Supercharge Your Productivity 32/518
- 28 Dec 2021 8 types of pricing models in software development outsourcing 31/464
- 01 Mar 2023 Bug Prioritization - What are the 5 levels of priority? 31/252
- 05 Jan 2024 Easy ASANA tips & tricks for you and your team 30/225
- 02 Nov 2022 Difference between Change Management and Project Management 30/259
- 10 Dec 2023 Pain points of User Acceptance Testing (UAT) 29/479
- 24 Nov 2023 The project management paradox: Achieving MORE by doing LESS 28/248
- 10 Nov 2022 Poor Code Indicators and How to Improve Your Code? 28/244
- 26 Sep 2024 Successful Project Management Techniques You Need to Look Out For 28/419
- 05 Jun 2023 Fractional, Part-Time (virtual) or Interim CTO: Who Will Cover Your Business Needs? 28/164
- 09 May 2022 Build one to throw away vs Second-system effect: What are differences? 27/337
- 18 Oct 2021 Key Elements to Ramping Up a Large Team 27/1247
- 23 Sep 2021 INFOGRAPHIC: Top 9 Software Outsourcing Mistakes 27/449
- 22 May 2022 What are common mistakes that new or inexperienced managers make? 26/304
- 06 Jun 2022 Change Management at the Project Level 26/330
- 18 Feb 2026 "Hit and Run" Project Management: Balancing Speed with Sustainability 26/39
- 11 Jan 2024 What are the Benefits and Limitations of Augmented Intelligence? 25/498
- 20 Jul 2022 Software Myths and Realities 24/935
- 13 Jan 2020 Quiz: Test your understanding project cost management 24/637
- 12 Mar 2024 How do you create FOMO in software prospects? 24/190
- 02 Dec 2021 3 Ways to Avoid Scope Creep in IT Consulting 23/228
- 19 Oct 2021 Is gold plating good or bad in project management? 23/845
- 19 Apr 2021 7 Most Common Time-Wasters For Software Development 22/565
- 17 Feb 2022 Prioritizing Software Requirements with Kano Analysis 22/325
- 17 Oct 2021 Does Fast Tracking increase project cost? 22/389
- 07 Dec 2023 12 project management myths to avoid 22/210
- 14 Jun 2022 Example and Excel template of a RACI chart in Software Development 21/857
- 26 Dec 2023 Improving Meeting Effectiveness Through the Six Thinking Hats 20/277
- 31 Oct 2021 Tips to Fail Fast With Outsourcing 20/406
- 01 Aug 2022 Is planning "set it and forget it" or "set it and check it"? 20/302
- 01 Mar 2024 10 Project Management Myths 19/163
- 30 Nov 2023 Project Managers, Focus on Outcomes — Not Deliverables 18/177
- 06 Nov 2019 How to Access Software Project Size? 16/262
- 14 Mar 2024 Why should you opt for software localization from a professional agency? 16/152
- 02 Jun 2024 Reviving Ancient Wisdom: The Spiritual Side of Project Management 16/250
- 21 Jun 2024 Dead Horses and the Escalation of Commitment 11/148
- 15 May 2022 20 Common Mistakes Made by New or Inexperienced Project Managers 11/292
- 10 May 2022 Levels of Teamwork 9/202
There are some managers who like to put schedule risk off onto the dev team. If the team gets behind, make them work more hours until they catch up. This practice is E.V.I.L. It is like if your director asked you, as manager, to pay the company back from your own paycheck if your team goes over budget. The budget is the same kind of prediction of the future as a software schedule is. And as manager you are just as responsible.
Estimating schedules is hard, because it is predicting the future. There is a school of thought that this practice is so hard that teams ought to refuse to do it.
How should you handle a developer who is not good at predicting the future? Should you punish them by making them work more hours? Or should you get them a better crystal ball in the form of some kind of class on scheduling?
If you have a developer who is wasting time, always has facebook open, spends all afternoon yakking with the other devs, takes extended smoking breaks, etc., you should definitely push them to work harder. (I mean, duh.) If your developers are at their desks doing the job of developing software, punishing them for being late is both cruel and counterproductive.
Explore more on these topics
Guest Blogging: The Definitive Guide
Top Trending Topics
Share This
Link copied!
Recently Updated News