How to Truly Embrace Agile: Lessons from a Hundred‑Person Development Team

Agile development is essentially a management culture for enterprises.

The biggest problem in the software industry today is that teams focus too much on the outward forms of agile—moving chairs, standing meetings, and tool‑driven iterations—while ignoring its original purpose.

True agile means team members work closely together, embrace change without arbitrary scope creep, and deliver incremental software to stay aligned with customer needs and market shifts.

Roles

Jeff Sutherland defines three Scrum roles: development team members, Scrum Master, and Product Owner.

Based on our practical experience we split roles into four categories:

Project Manager – similar to a servant‑leader Scrum Master, coordinates collaboration, runs stand‑ups, and removes obstacles without dictating how developers should work.

Product Manager – equivalent to Product Owner, decides what to build, creates the backlog, and prioritises items, focusing on the 20% of features that deliver 80% of value.

Developer – implements tasks, reports progress, and completes assigned work.

Tester – designs test plans, writes test cases, and manages defects.

Using CORNERSTONE for Agile Management

In CORNERSTONE we assign roles and permissions according to each member’s function.

Before a project starts, the Product Manager writes user stories that follow the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable). The platform lets us link related stories, test cases, and iterations, set priorities, and define start/end dates.

During sprint planning, the Product Owner explains the backlog and the team breaks each story into small, implementable tasks that one developer can finish within a sprint.

After the sprint starts, we hold a daily 15‑minute stand‑up using the CORNERSTONE board view.

Each member answers three questions: what they did yesterday, what they will do today, and any blockers. The Project Manager focuses on removing those blockers.

Yesterday’s work

Today’s plan

Potential impediments

Project managers monitor progress via dashboards, burndown charts, defect distribution, and cumulative defect trends.

The built‑in Gantt chart shows iteration timelines and task assignments, ensuring balanced workload.

Administrators can also generate reports covering burndown, code commits, status distribution, daily trends, and team member hours.

At the end of each sprint we hold an evaluation meeting where the team demos completed work, receives feedback, and assesses task completion versus commitment.

In summary, agile is a management approach, not a prescriptive checklist. As Jeff Sutherland said, “Don’t guess—plan, do, check, act.” This captures the essence of true agile practice.