Key Elements to Ramping Up a Large Team
Last updated: December 25, 2023 Read in fullscreen view
Recommended for you
- 01 Aug 2024
The Standish Group report 83.9% of IT projects partially or completely fail 150/1772 - 13 Apr 2024 Lessons on Teamwork and Leadership from Chinese story book "Journey to the West" 41/949
- 28 Oct 2023 The GOLDEN Rules of Software Engineering 27/522
- 02 Nov 2021 What is Terms of Reference (ToR)? 23/1466
- 08 Dec 2021 What Are The 4 Types of Maintenance Strategies? 20/1031
- 03 Apr 2022 Microsoft Solutions Framework (MSF) 12/1157
- 12 Oct 2022 14 Common Reasons Software Projects Fail (And How To Avoid Them) 10/504
- 13 Oct 2021 What is Bug Convergence? Why is it important for User Acceptance Testing (UAT)? 8/684
- 02 Dec 2022 3 Levels of Quality in KANO Analysis Model 8/1000
- 18 Dec 2023 The Cone of Uncertainty in Scrum & Requirement Definition 8/643
- 13 May 2022 IT Training and Development: The most effective options for upskilling IT staff 7/1021
- 14 Oct 2021 Stream Story - Low land stream or fast moving stream? 6/569
- 13 Oct 2021 Outsourcing Software Development: MVP, Proof of Concept (POC) and Prototyping. Which is better? 6/424
- 28 Jul 2022 POC, Prototypes, Pilots and MVP: What Are the Differences? 6/606
- 31 Aug 2022 What are the best practices for software contract negotiations? 5/215
- 05 Mar 2021 How do you minimize risks when you outsource software development? 5/317
- 07 Oct 2025 Case Study: Using the “Messaging House” Framework to Build a Digital Transformation Roadmap 5/45
- 05 May 2021 TIGO Magic Scale - PoC tool for you to apply dichotomous thinking before submitting RFP 4/297
- 12 Dec 2021 Zero Sum Games Agile vs. Waterfall Project Management Methods 4/374
- 20 Jul 2022 Software Myths and Realities 4/797
- 04 Oct 2022 Which ERP implementation strategy is right for your business? 4/278
- 03 Nov 2022 Questions and answers about Kano Model 3/805
- 18 Jul 2021 How To Ramp Up An Offshore Software Development Team Quickly 3/516
- 10 Apr 2024 The Parking Lot Method: Unlocking a Simple Secret to Supercharge Your Productivity 3/403
- 01 Dec 2023 Laws of Project Management 3/249
- 04 Mar 2023 [Medium] Box-Ticking: The Management Strategy That’s Killing your Productivity 3/518
- 05 Sep 2023 The Cold Start Problem: How to Start and Scale Network Effects 3/167
- 07 Jul 2022 Managing Project Execution Terms 3/379
- 05 Jun 2023 Fractional, Part-Time (virtual) or Interim CTO: Who Will Cover Your Business Needs? 2/109
- 26 Sep 2024 Successful Project Management Techniques You Need to Look Out For 2/368
- 02 May 2022 What Is RAID in Project Management? (With Pros and Cons) 2/734
- 24 Nov 2023 The project management paradox: Achieving MORE by doing LESS 2/193
- 01 May 2024 Warren Buffett’s Golden Rule for Digital Transformation: Avoiding Tech Overload 2/188
- 28 Oct 2022 Build Operate Transfer (B.O.T) Model in Software Outsourcing 2/361
- 04 Oct 2021 Product Validation: The Key to Developing the Best Product Possible 2/295
- 15 May 2022 20 Common Mistakes Made by New or Inexperienced Project Managers 2/247
- 12 Aug 2022 What is End-to-end project management? 2/382
- 14 Jun 2022 Example and Excel template of a RACI chart in Software Development 2/707
- 22 May 2022 What are common mistakes that new or inexperienced managers make? 1/243
- 27 Jan 2020 Should a project manager push developers to work more hours due to mistakes of manager schedule setting? 1/412
- 01 Oct 2020 Handling tight project deadlines as a business analyst 1/313
- 07 Dec 2023 12 project management myths to avoid 1/167
- 01 Mar 2024 10 Project Management Myths 1/120
- 12 Aug 2024 Understanding Google Analytics in Mumbai: A Beginner's Guide 1/84
- 01 Aug 2022 Is planning "set it and forget it" or "set it and check it"? /264
- 06 Mar 2024 [SemRush] What Are LSI Keywords & Why They Don‘t Matter /131
- 30 Nov 2023 Project Managers, Focus on Outcomes — Not Deliverables /143
- 02 Nov 2022 Difference between Change Management and Project Management /216
- 23 Jun 2024 Best Practices for Managing Project Escalations /183
- 21 Jun 2024 Dead Horses and the Escalation of Commitment /123
- 02 Jun 2024 Reviving Ancient Wisdom: The Spiritual Side of Project Management /204
- 19 Oct 2021 Software development life cycles /628
- 11 Oct 2021 10 Myths About Low-End Project Management Software /274
- 13 Jan 2020 Quiz: Test your understanding project cost management /568
- 17 Oct 2021 Does Fast Tracking increase project cost? /348
- 02 Dec 2021 3 Ways to Avoid Scope Creep in IT Consulting /192
- 09 May 2022 Build one to throw away vs Second-system effect: What are differences? /297
- 10 May 2022 Levels of Teamwork /180
- 06 Jun 2022 Change Management at the Project Level /292
- 03 Jan 2023 Organizing your agile teams? Think about M.A.T (Mastery, Autonomy, Purpose) /333
In today's environment, it's critical to ramp up large teams quickly and efficiently to ensure your customers, whether internal or external, are pleased with the end deliverable.
WHAT IS RAMP UP IN PROJECT?
A sudden increase in resource requirement is known as ramp up. The resource manager identifies and allocates the appropriate resources to fulfill the resource requests. Ramp-up occurs during “execution” stage when additional resources are needed to complete different tasks.
"A properly ramped up team provides many benefits, least of which is a project being completed successfully, on time, on budget, and with great quality," says Innovative Learning Group Project Manager Gayle Holsworth. "This will allow the team to focus on creating solutions that truly improve performance and business results."
MYTHICAL MAN-MONTH - ADDING MANPOWER CAN SHORTEN RAMP-UP TIME?
These Brooks quotes, author of the Mythical man month are:
Adding manpower to late software projects delays them further.
It takes some time for the people added to a project to become productive. Brooks calls this the “ramp up” time. Software projects are complex engineering endeavors, and new workers on the project must first become educated about the work that has preceded them; this education requires diverting resources already working on the project, temporarily diminishing their productivity while the new workers are not yet contributing meaningfully. Each new worker also needs to integrate with a team composed of several engineers who must educate the new worker in their area of expertise in the code base, day by day. In addition to reducing the contribution of experienced workers (because of the need to train), new workers may even make negative contributions, for example, if they introduce bugs that move the project further from completion.
The problems associated with adding new teams is ramping up, individuals need to learn/understand
- Business logic
- Project processes
- Best resources for situations
- Project politics
- Collaborate with others
A scrum team takes 2 sprints to get up to speed, usually 50% efficiency for sprint 1 and 60/70% in Sprint 2. When you add the added overhead of trying to collaborate with other teams this can slow new teams further and slow existing teams.
TIPS ON HOW TO RAMP UP A LARGE TEAM
Staffing
Select team members with the right skills and experience in the industry, subject, delivery method, and role they're playing on the project. Most important, choose a dedicated, qualified project manager.
Process
Figure out the steps you want to follow, and map out the phases and milestones. Determining project steps is critical to creating an accurate schedule.
Be sure that ramping up a large team doesn't happen too fast which falls in the trap of Brook's law.
Communication
Decide, as a team, how and when to communicate. A project can rise and fall, be best in class, or be just average, based on communication.
Quality
Ensure the team knows the project owner's and stakeholders' quality expectations. No one ever started a project by saying, "we need to strive for poor quality."
Schedule
Understand how the work is done and how long each step will take so you don't just add random dates to a plan.
Budget
Ensure the team understands the budget for which it has responsibility. If you develop an awesome solution, but it costs double the original budget, it probably won't help the organization.
Templates
Establish working and deliverable templates, which are built using the appropriate software and branded for the initiative, prior to starting the project.
Facilities
Determine the physical space(s) and location(s) needed to complete the project. Do you need a dedicated "war room," storage space for materials, etc.?
Equipment
Ensure the team has access to the equipment the training is being developed for, e.g., a medical device, software program, etc. If the team can't "work" with actual equipment, it's difficult to create practice that mirrors real-world application.
LAST, BUT NOT LEAST
Every client wants to get their offshore software team going quickly. In this video, Dave discusses ways to grow the team without chaos or killing morale.
Via Innovative Leading Group
Explore more on these topics
Guest Blogging: The Definitive Guide
Top Trending Topics
Share This
Link copied!