# Agile & Scrum > Selected Engineer ApS work demonstrating Agile & Scrum — the achievements that prove it. - [Saved 4,000 hours by mentoring and growing a team from 2 to 18 members, optimizing workflows and fostering cross‑departmental collaboration.](https://engineer.company/portfolio/saved-4-000-hours-by-mentoring-and-growing-26/) - [Designed and managed 5,000 hours of map development, utilizing Agile methodologies such as Scrum and Jira for effective project management.](https://engineer.company/portfolio/designed-and-managed-5-000-hours-of-map-29/) - [Gathered and analyzed business requirements to translate into actionable features and user stories aligned with data governance standards.](https://engineer.company/portfolio/gathered-and-analyzed-business-requirements-to-translate-into-31/) - [Managed the execution of 30 successful GIS projects, demonstrating leadership in delivering innovative solutions across the field.](https://engineer.company/portfolio/managed-the-execution-of-30-successful-gis-projects-32/) - [Led company growth from 4 to 14 employees by employing Agile methodologies and effective project management practices.](https://engineer.company/portfolio/led-company-growth-from-4-to-14-employees-33/) - [Improved team communication and collaboration by implementing Slack, Mattermost, 1Password, and Jira, saving 8,000 hours of labor.](https://engineer.company/portfolio/improved-team-communication-and-collaboration-by-implementing-slack-34/) - [Enhanced project efficiency, saving 150 hours per month across 30 projects by optimizing workflows and resource management.](https://engineer.company/portfolio/enhanced-project-efficiency-saving-150-hours-per-month-46/) - [Ran the site's development as 49 written initiatives across 52 plan documents, each carrying its open boxes, its measurements and the decisions it declined — including six of eight agent‑readiness findings refused with the reason recorded.](https://engineer.company/portfolio/ran-development-as-49-written-initiatives-141/) - [Held four repositories to one history standard — conventional, emoji‑free, no attribution trailers, enforced by a commit‑message hook — alongside 46 instruction documents that govern how the work is done.](https://engineer.company/portfolio/held-five-repositories-to-one-history-standard-165/)