Agile Organization: What It Means for Employers

What it means in practice

What the term means. No federal statute or regulation defines an agile organization, so the meaning comes from practice. GAO describes agile as "an approach to software development that encourages collaboration across an organization and allows requirements to evolve as a program progresses," built on iterative delivery in short stages with continuous customer feedback. GAO traces it to incremental development used since the 1950s, Scrum (1995) and the Agile Manifesto of 2001, followed by frameworks such as Kanban and DevOps. When a whole company adopts these habits beyond its software teams, people call it an agile organization. Federal regulations do use "agile" as a goal: VA lists "Agile" among its core characteristics, meaning it "anticipates and adapts quickly to current challenges and new requirements" (38 CFR 0.602). It is an aspiration and sets no duties for private employers.

How the teams work. In GAO's description of Scrum, a product owner represents the customer, sets priorities and accepts finished work. Work runs in timed iterations called sprints, the team meets for daily stand-ups, shows completed work at the end of each sprint, and holds a retrospective on lessons learned. Each habit raises HR questions about supervision, paid time, job descriptions and cut roles.

Where agile sits in federal law and policy. The Federal Information Technology Acquisition Reform Act (FITARA) directs OMB to require, in its IT capital planning guidance, that each covered agency's Chief Information Officer certify that IT investments are adequately implementing incremental development as OMB defines it (40 U.S.C. 11319). GAO notes that more agencies adopted agile as a result: DHS announced five agile pilot programs in 2016, and at least 22 Department of Defense major defense acquisition programs reported using agile methods in 2020. GAO's Agile Assessment Guide (GAO-24-105506) is written mainly for federal auditors, though GAO says other organizations can use it too.

What GAO found about the people side. GAO's 2012 review of five agencies listed effective practices that included empowering small, cross-functional teams and obtaining frequent stakeholder feedback. Several of its 14 challenges were workforce issues: "Teams had difficulty collaborating closely," "Teams had difficulty transitioning to self-directed work," "Agencies had trouble committing staff," and "Staff had difficulty committing to more timely and frequent input." GAO's 2020 spotlight on agile adds that organizations need a dedicated agile team, "which is a challenge when there is an insufficient number of staff, or when staff have several simultaneous duties," and that staff should be "appropriately trained in Agile methods."

Job descriptions when roles change. OPM's classification rules apply only to federal positions, but they show the discipline a reorganization requires. OPM defines a position description as "a statement of the major duties, responsibilities, and supervisory relationships of a given position," and says it "must be kept up to date." Positions are classified "on the basis of the duties actually performed." Temporary duties usually do not change the series or grade, but the position "should be reevaluated" if they last several months and are likely to recur, and a position classified on projected duties should be reviewed about six months after the work begins. OPM notes that duties most often change because of "reorganizations, new or revised organizational responsibilities or missions, and changes in technology." Its December 2025 project manager template guidance names Agile among the methodologies a project manager may use and tells agencies to update descriptions for practices such as Agile and DevSecOps while keeping to classification standards.

Cross-functional teams and federal job series. OPM's 2019 project manager guidance says positions are not multidisciplinary just because "members of a work team with varied but complimentary competencies and experiences collaborate on a multifaceted problem or project." In an April 24, 2026 memo, OPM began consolidating low-use occupational series to support "workforce agility," and said consolidation "will not automatically change an employee's grade, pay, tenure, or career ladder placement" and that agencies must meet collective bargaining notice and negotiation duties.

Overtime exemptions when titles flatten. Agile structures often remove layers of managers and add roles such as product owner or team lead. Under the Fair Labor Standards Act, a title does not decide exempt status; duties do. An exempt executive must have management as the primary duty, run "a customarily recognized department or subdivision," direct two or more other employees, and have hiring or firing authority or recommendations given "particular weight" (29 CFR 541.100). A recognized unit needs "a permanent status and a continuing function," which separates it from "a mere collection of employees assigned from time to time to a specific job." The rules also say a manager does not lose the exemption "merely because the employee draws and supervises workers from a pool or supervises a team of workers drawn from other recognized units" (29 CFR 541.103). Primary duty means "the principal, main, major or most important duty," judged on all the facts, and more than 50 percent of time on exempt work is a useful but not a required guide (29 CFR 541.700). A working supervisor whose primary duty is production work does not become exempt by sometimes directing others (29 CFR 541.106). For the broader tests, see exempt vs. non-exempt.

Example: shared supervision in a matrix. Supervision can be split, but each exempt executive must direct two full-time employees or the equivalent, and "Hours worked by an employee cannot be credited more than once for different executives" (29 CFR 541.104). Suppose a squad lead and a chapter lead both oversee the same two full-time developers. Shared supervision of the same two employees does not satisfy the rule for either lead. If instead each developer splits the week, four hours a day under each lead, each developer counts as a half-time employee for both leads. A lead who also directs one other full-time developer would then direct 1 + 0.5 + 0.5 = 2 full-time equivalents and meet the headcount test, although the other duty and salary tests still apply.

Software roles. Computer systems analysts, programmers and software engineers can be exempt as professionals if paid at least $684 a week on a salary or fee basis, or at least $27.63 an hour, and if their primary duty is systems analysis or the design, development, testing or modification of computer systems or programs. The rule says "job titles are not determinative" (29 CFR 541.400).

Stand-ups, retrospectives and training time. For non-exempt team members, meetings and training count as working time unless all four conditions are met: attendance is outside regular hours, it is in fact voluntary, the meeting is not directly related to the job, and no productive work is done (29 CFR 785.27). Attendance is not voluntary if the employer requires it or the employee is led to believe that skipping it would hurt their job (29 CFR 785.28). Training is directly related to the job if it is "designed to make the employee handle his job more effectively" (29 CFR 785.29). Example: a non-exempt tester who joins a required 15-minute daily stand-up before the shift adds 75 minutes of work over a five-day week. See hours worked.

Self-managed teams and labor law. The National Labor Relations Act defines a labor organization to include "any agency or employee representation committee or plan" in which employees participate and that deals with employers about "grievances, labor disputes, wages, rates of pay, hours of employment, or conditions of work" (29 U.S.C. 152(5)). An employer may not "dominate or interfere with the formation or administration of any labor organization or contribute financial or other support to it" (29 U.S.C. 158(a)(2)). A delivery team that plans its own work is a different thing from a committee that negotiates pay or schedules with management. Where employees have a union, the duty to bargain covers "wages, hours, and other terms and conditions of employment" (29 U.S.C. 158(d)). The union and employee engagement pages cover these rules in more depth.

Disability rules when tasks rotate. Cross-training and shared backlogs change which duties are essential. Under the ADA regulations, essential functions are "the fundamental job duties" of a position, not its marginal functions. A function may be essential because of "the limited number of employees available among whom the performance of that job function can be distributed." Evidence includes the employer's judgment, "written job descriptions prepared before advertising or interviewing applicants," time spent on the function and the experience of past and current incumbents. Reasonable accommodation can include "job restructuring" and "reassignment to a vacant position" (29 CFR 1630.2(n) and (o)).

Fair selection in a reorganization. The EEOC says it is illegal to make decisions about job assignments and promotions based on race or other protected traits, that "an employer may not choose the oldest workers because of their age" when deciding layoffs, and that training programs may not discriminate. Choosing who joins a new team, who is retrained and whose role is cut are therefore covered decisions. See disparate treatment and adverse impact.

When restructuring cuts jobs. The federal WARN Act covers businesses with 100 or more employees, excluding part-time employees, or 100 or more employees who together work at least 4,000 hours a week (20 CFR 639.3(a)). An "employment loss" includes a termination other than for cause, voluntary departure or retirement, a layoff over 6 months, or a cut of more than 50 percent in an employee's hours in each month of any 6-month period. A relocation or consolidation is not an employment loss if the employer offers a transfer within reasonable commuting distance with no more than a 6-month break (20 CFR 639.3(f)). Employers must look 90 days ahead and behind to see whether smaller rounds add up to a covered event, unless they show the losses had "separate and distinct actions and causes" (20 CFR 639.5). Notice details are on the offboarding page.

Example: rolling cuts. A site with 140 full-time employees eliminates 30 roles in March and 25 more in May, within 90 days. Neither round reaches 50 on its own, but together they total 55 employees, or about 39 percent of the site (55 / 140). That exceeds both the 50-employee and the 33 percent thresholds for a mass layoff (20 CFR 639.3(c)), so the rounds are treated together unless the employer can show separate causes.

Where states differ. State WARN laws can reach smaller cuts. As one example, the New York State Department of Labor says its law covers private businesses with 50 or more full-time employees in the state and requires 90 days' notice, including for mass layoffs of 25 or more full-time employees who make up at least 33 percent of the site. A cut of 25 at a 70-person New York site (about 36 percent) can therefore require state notice even though it is below the federal 50-employee floor. As a second example, California's Employment Development Department says its law covers establishments with 75 or more full- and part-time employees and treats a layoff of 50 or more within 30 days as a mass layoff "regardless of % of workforce," with 60 days' notice.

Does agile change who is exempt? Not by itself. Exempt status turns on salary and duties under 29 CFR part 541, so an employer has to check each redesigned role against those tests. Must job descriptions be rewritten? No federal law requires private employers to keep job descriptions, but the ADA treats descriptions written before hiring as evidence of essential functions, and OPM requires federal descriptions to stay current. Are required agile workshops paid? For non-exempt staff, yes, because required attendance is not voluntary (29 CFR 785.28).

Why it matters and common mistakes

How Remindax helps

Related terms

See all terms in Workforce Trends & Culture or browse the full HR Glossary.