
Key Elements to Ramping Up a Large Team
Last updated: December 25, 2023 Read in fullscreen view



- 02 Nov 2021
What is Terms of Reference (ToR)? 1001
- 03 Apr 2022
Microsoft Solutions Framework (MSF) 780
- 08 Dec 2021
What Are The 4 Types of Maintenance Strategies? 677
- 01 Aug 2024
The Standish Group report 83.9% of IT projects partially or completely fail 642
- 13 May 2022
IT Training and Development: The most effective options for upskilling IT staff 635
- 02 Dec 2022
3 Levels of Quality in KANO Analysis Model 607
- 19 Oct 2021
Software development life cycles 584
- 20 Jul 2022
Software Myths and Realities 537
- 13 Apr 2024
Lessons on Teamwork and Leadership from Chinese story book "Journey to the West" 516
- 02 May 2022
What Is RAID in Project Management? (With Pros and Cons) 477
- 13 Jan 2020
Quiz: Test your understanding project cost management 455
- 03 Nov 2022
Questions and answers about Kano Model 453
- 14 Oct 2021
Stream Story - Low land stream or fast moving stream? 436
- 28 Jul 2022
POC, Prototypes, Pilots and MVP: What's the differences? 421
- 14 Jun 2022
Example and Excel template of a RACI chart in Software Development 406
- 18 Dec 2023
The Cone of Uncertainty in Scrum & Requirement Definition 405
- 13 Oct 2021
What is Bug Convergence? Why is it important for User Acceptance Testing (UAT)? 399
- 27 Jan 2020
Should a project manager push developers to work more hours due to mistakes of manager schedule setting? 362
- 18 Jul 2021
How To Ramp Up An Offshore Software Development Team Quickly 362
- 12 Oct 2022
14 Common Reasons Software Projects Fail (And How To Avoid Them) 348
- 28 Oct 2022
Build Operate Transfer (B.O.T) Model in Software Outsourcing 290
- 01 Oct 2020
Handling tight project deadlines as a business analyst 285
- 13 Oct 2021
Outsourcing Software Development: MVP, Proof of Concept (POC) and Prototyping. Which is better? 279
- 12 Aug 2022
What is End-to-end project management? 275
- 05 Mar 2021
How do you minimize risks when you outsource software development? 270
- 03 Jan 2023
Organizing your agile teams? Think about M.A.T (Mastery, Autonomy, Purpose) 270
- 17 Oct 2021
Does Fast Tracking increase project cost? 259
- 07 Jul 2022
Managing Project Execution Terms 257
- 12 Dec 2021
Zero Sum Games Agile vs. Waterfall Project Management Methods 254
- 09 May 2022
Build one to throw away vs Second-system effect: What are differences? 245
- 28 Oct 2023
The GOLDEN Rules of Software Engineering 240
- 04 Mar 2023
[Medium] Box-Ticking: The Management Strategy That’s Killing your Productivity 233
- 26 Sep 2024
Successful Project Management Techniques You Need to Look Out For 223
- 05 May 2021
TIGO Magic Scale - PoC tool for you to apply dichotomous thinking before submitting RFP 222
- 06 Jun 2022
Change Management at the Project Level 221
- 22 May 2022
What are common mistakes that new or inexperienced managers make? 212
- 04 Oct 2021
Product Validation: The Key to Developing the Best Product Possible 198
- 04 Oct 2022
Which ERP implementation strategy is right for your business? 188
- 15 May 2022
20 Common Mistakes Made by New or Inexperienced Project Managers 179
- 01 Aug 2022
Is planning "set it and forget it" or "set it and check it"? 174
- 31 Aug 2022
What are the best practices for software contract negotiations? 166
- 02 Dec 2021
3 Ways to Avoid Scope Creep in IT Consulting 150
- 11 Oct 2021
10 Myths About Low-End Project Management Software 133
- 10 Apr 2024
The Parking Lot Method: Unlocking a Simple Secret to Supercharge Your Productivity 124
- 10 May 2022
Levels of Teamwork 116
- 07 Dec 2023
12 project management myths to avoid 113
- 01 May 2024
Warren Buffett’s Golden Rule for Digital Transformation: Avoiding Tech Overload 107
- 05 Sep 2023
The Cold Start Problem: How to Start and Scale Network Effects 107
- 02 Jun 2024
Reviving Ancient Wisdom: The Spiritual Side of Project Management 106
- 24 Nov 2023
The project management paradox: Achieving MORE by doing LESS 101
- 30 Nov 2023
Project Managers, Focus on Outcomes — Not Deliverables 99
- 02 Nov 2022
Difference between Change Management and Project Management 89
- 21 Jun 2024
Dead Horses and the Escalation of Commitment 84
- 06 Mar 2024
[SemRush] What Are LSI Keywords & Why They Don‘t Matter 84
- 05 Jun 2023
Fractional, Part-Time (virtual) or Interim CTO: Who Will Cover Your Business Needs? 76
- 01 Dec 2023
Laws of Project Management 76
- 23 Jun 2024
Best Practices for Managing Project Escalations 54
- 01 Mar 2024
10 Project Management Myths 47
- 12 Aug 2024
Understanding Google Analytics in Mumbai: A Beginner's Guide 37
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
