Agile Project Management

A simple and easy-to-understand use of Kanban with tasks and estimates.

How we Work

Project Management

We use GitHub for both source control and project management.

We create a code repository and project for you in GitHub

We will invite you as a Collaborator to a new repository in the NextOps-io GitHub Org.

You upload your tasks

Start adding your tasks to the Kanban board's Backlog. By all means add a requirements document (see Step 3).

Check that the services you are after correspond with the plan you are on.

We break down the tasks into smaller chunks of work

We will estimate the complexity of the tasks and break then down into smaller tasks accordingly. We find AI is very good at this but all team members, including you as the client and `product owner` get a voice. Estimates help everyone with expectations and, over time, establish the velocity at which we can work.

You manage the priority of tasks on the Backlog

Estimates may change your priorities and you may choose to re-order tasks. An engineer will then take the top task off the Backlog and start work.

Rinse and repeat.

With our unique, Unlimited plans, you can simply add new tasks as, and when, you like and an engineer will work through them, one at a time and always working from the top of the Backlog.

Agile Project Planning in GitHub

Got questions?

Schedule a call to see if NextOps is a fit for your business.

Project Management FAQ

Frequently Asked Questions

How we work

We use Jira, Trello, Azure Devops etc. Can we use that for Project Management?

At this stage, we are using GitHub for both code hosting and project management due to the richness of the GitHub APIs as well as the universal popularity of the platform. We will look at the possibility of supporting other project managers as the business matures.

Our code is in Azure DevOps, Bitbucket, GitLab etc. Can you push the code there?

As with project management, GitHub is the logical choice to start out offering our service and to reliably automate onboarding and handovers. The above are, once again, possibilities we can look at as the business matures.

How do I get on-boarded?

There is a field for your GitHub username in the payment page when you first sign up. This is the user we will invite as a Collaborator to your initial repository.

Can we communicate on Slack, Teams, Discord etc ?

Our communications are necessarily asynchronous and take place via Issues, Discussions and Pull Requests inside the GitHub project in your initial repository.

How many repositories are provided?

Repositories are provided as-needed and to meet technical needs and best practices. So, we would create a repository for `infrastructure` and another for each and every containerized application. For Kubernetes and some other use-cases, we would also create `configuration` repositories.

How are the project deliverables transferred

The repositories can be transferred to your organisation at project completion. You will only want to do this if you are sure you that we will not be making further changes (ie unlikely in most cases). A good middle ground is to `fork` a repository and, of course, you can clone a repository at any time. How a transfer works in practice depends on GitHub and for full information please refer to

Can you help us with solution design?

NextOps only provides 'Day 1' work, that is, creating the infrastructure and application code which are also the development and testing stages of the Software Delivery Lifecycle (SDLC). It is important to know that NextOps does not do Infrastructure or Application design.

Can you monitor and manage the solution?

We don't plan to support maintenance and monitoring for Cloud resources. We fill a key niche by doing the development and testing work for Infrastructure as Code and Containers'.


Cloud infrastructure and container images, on-tap.

NextOps is <code \> for the Cloud