If you’ve ever wondered whether there is one crucial and indisputable theory regarding a project life cycle, you’ve probably noticed there is not. Depending on a time and an industry each concept refers to, there are so many different views on that issue that you may feel dizzy. Let’s focus on the approach we stick to while agile software development. How does such projects’ life cycle look like and what kind of deliverables we provide at each step?
That’s the very first step we take before the project starts. Our Product Owner and tech lead have a meeting or a video conversation with a client so they can discuss the needs, get a bigger picture of the problems that client want to solve and advise the best solution which fits them.
At this stage of the project life cycle, goals are specified and decisions on the final feature scope are made. It ends with fulfilling the formalities and then the work starts.
People involved: Salesperson, Product Owner, Tech Lead
What is needed: Client’s brief (especially problems to solve, goals, requirements), benchmarks
Deliverables: high-level project description (scope), measurable objectives and risks, budget and deadline established, contract signed up
When we have the business analysis stage closed, we step into an input phase. It means we put finishing touches on the project idea and precise the scope. We want to make sure that the information we got from the client our analysis is understandable for both sides. Then we are able to prepare a time estimation and explicit the cost.
It’s also a time when a backlog and first designs are created to give the client a first look & feel of the project Usually it takes between one and two development sprints (one or two weeks) what is quite a short amount of time considering such an important phase in the whole project life cycle.
People involved: Product Owner, UX/UI designers, Tech Lead and the salesperson
What is needed: the precise project’s brief, market and competitors’ analysis, benchmarks, style preferences
Deliverables: a mutually agreed project scope and first designs
As we work in Scrum methodology, that’s an iterative process. People assigned to particular project start working on their tasks and after every one or two-week sprint they have a sprint review with a client so both sides can ensure the job is pushing forward in the right direction.
People involved: Developers, Tech Lead, UX/UI Designers, Product Owner
What is needed: prioritized and assigned tasks
Deliverables: part of the final product after every sprint finished
When the job is done and we can’t wait for the product to say ‘hello’ to the world, there is a project closure phase: deployment. We test the system: check the servers, domains and production environment, finishing the documentation and deploy the product into the live environment.
People involved: Developers, Tech Lead, Testers, Product Owner
Deliverables: the final product which meets a client’s requirements and is in accordance with the contract
We believe that the project life cycle has no obvious ending. From our point of view, the part of the closure phase is a support: maintaining and improving a product. Our specialists watch over to stay it works properly and are at your disposal if you decide to boost it – and if so, the whole process starts from the beginning.
I’m full of hope you’ve found this information useful. If you’re interested in project management, I’d strongly recommend you to read what really matters while working on the project in Scrum.