Owner
Credissimo
Status
finished
current: active
Duration
6 months
Role
IT Project Manager
Process Structure
- A business stakeholder (usually, the Team lead of the business department) sends request via official communication channels (email, JIRA).
- The request is allocated to the project manager, responsible for the project, categorised, and added to the product backlog.
- The Project Manager describes the request to the product backlog for the project as a new epic with user stories, or as user stories under existing epic, analyse it, discuss it with the Product Owner, and clarify details with the requester and other stakeholders, if necessary.
- The Project Manager adds detailed descriptions, acceptance criteria, and other information, like designs, or Excel tables (if necessary) to the created user stories. In some cases, creates particular tasks.
- The Project Manager organise a Grooming meeting with the Product Owner and IT team for discussion, clarification, prioritisation, and estimation of the new tasks.
- On a Sprint Planning meeting between the Project Manager and Product Owner, based on the allocated priority and time estimation, the request is added to the sprint.
- The Project Manager leads Daily Scrum meetings with the IT team for tracking the progress and solving issues for the tasks, added to the sprint.
- At the end of the sprint, after receiving confirmation from the developers and QAs that all sprint tasks are ready and tested, the Project Manager organises a Demonstration meeting wit the Product Owner and involved stakeholders for demonstration of the new features, and receiving acceptance for release on Production environment.
- The Project Manager updates the business documentation for the project, based on the newly added features, prepare training materials and organise training sessions for all affected business departments.
- On the Release date sends information to the all business departments for the new features added.
- The Project Manager organises a Sprint Review meeting with the IT team, and optionally, the Product Owner.
Methodology
Custom working approach, based on the Scrum methodology
Activities
- Observation of the work of the IT department, and the challenges they have on daily basis; getting insights and propositions of the technical team for improving the working processes.
- Observation of the work of the each business department and Interviewing the people there – what technical challenges they meet, when need technical support, from where receive information for the new features, etc.
- Introducing new business roles:
- Project Manager as a single point of technical contact from the Product Owner and Product Managers.
- Product Owner as a main contact person and decision maker for introducing of new features, regarding a product.
- Product Manager – the Business departments Team Lead, who is a subject matter expert in the particular business, and is aware of the challenges their team meets on everyday basis.
- Setup JIRA project for maxo.bg project, introduce Confluence for business flows description, and tracking the JIRA tasks progress.
- Introducing working on bi-weekly sprints with respective meetings during the sprints: Backlog Grooming, Scrum Planning, Daily Scrum, Demonstration, and Sprint Review meetings.
- Preparing full business documentation for maxo.bg, split by business areas (Application process with document templates, Processing Application with integrations, Collection process, etc.) with added decision flow diagrams for better understanding.
- Preparing and maintaining a full training documentation by business department, available on Confluence, exported as PDFs and printed on paper.
Tools
- JIRA
- Confluence
- Microsoft Office Package (MS World, MS Excel, MS Outlook)

