Project Management (Agile)
Getting it delivered
Somebody accountable for scope, dates and the awkward conversations, so a project has one owner instead of five opinions.

Photo: hudsoncrafted / Pixabay 
Photo: taniadimas / Pixabay
Selected work demonstrating this service.
-
Saved 4,000 hours growing a team from 2 to 18
Saved 4,000 hours by mentoring and growing a team from 2 to 18 members, optimizing workflows and fostering cross‑departmental collaboration.
-
Managed 5,000 hours of map development
Designed and managed 5,000 hours of map development, utilizing Agile methodologies such as Scrum and Jira for effective project management.
-
Gathered and analyzed business requirements
Gathered and analyzed business requirements to translate into actionable features and user stories aligned with data governance standards.
-
Managed 30 successful GIS projects to delivery
Managed the execution of 30 successful GIS projects, demonstrating leadership in delivering innovative solutions across the field.
-
Led company growth from 4 to 14 employees
Led company growth from 4 to 14 employees by employing Agile methodologies and effective project management practices.
-
Improved team communication and collaboration
Improved team communication and collaboration by implementing Slack, Mattermost, 1Password, and Jira, saving 8,000 hours of labor.
-
Guided company projects through development
Guided the execution of numerous company projects, offering expert support in the software development phases.
-
Overhauled internal processes, saving 8,000 hours
Overhauled internal processes, saving 8,000 hours by improving software architecture, systems, and scheduling efficiency.
-
Established a Technical Support department
Established a Technical Support department, servicing over 10,000 clients with IT support and troubleshooting solutions, tracking client requests in a CRM.
-
Saved 150 hours a month across 30 projects
Enhanced project efficiency, saving 150 hours per month across 30 projects by optimizing workflows and resource management.
-
Delivered analysis and regular progress reports
Delivered analysis and regular progress reports to the CEO, translating engineering KPIs and delivery status into decisions.
-
Designed a time‑management and reporting system
Designed a time‑management and reporting system that remained in production use for years without significant modification.
-
Automated team collaboration
Automated team collaboration, password management, task and time management, and built a semi‑automatic project‑showcase system, raising team productivity.
-
Ran development as 51 written initiatives
Ran the site's development as 51 written initiatives across 54 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.
-
Put the documentation under its own linter
Put the documentation under its own linter — a per‑file line budget that only ratchets down, an index requirement and a real‑path check — which found six of nine plans marked done while carrying unchecked boxes, and fourteen commit‑gating tasks named in no document.
-
Held 4 repositories to one history standard
Held four repositories to one history standard — conventional, emoji‑free, no attribution trailers, enforced by a commit‑message hook — alongside 48 instruction documents that govern how the work is done.
If this is the work you need done, the next step is a conversation.
Tell us the problem and we will tell you honestly whether we are the right people.

