Project Summary

Project Summary

1. What Went Well

Team and Collaboration

• Each team member successfully fulfilled their assigned roles:
  • Arkadi: Project Manager, Communication Lead, Developer
  • Nikita: Developer, Requirements Engineer, Documentation Manager, Tester, DevOps Engineer
  • Artemi: Requirements Engineer, Tester
  • Alina: Requirements Engineer, Tester
• Strong initial planning ensured a smooth onboarding phase, setting up tools like GitHub, Wiki, and CI/CD pipelines.
• Team spirit and shared problem-solving improved efficiency, especially during critical stages like integration testing.

Project Development Process

• Effective use of Agile methodology with clearly defined iterations.
• Core functionality was implemented on time due to robust requirement elicitation and thorough user story development.
• Successful integration of Docker, Java Spring, and PowerShell enabled a reliable backend infrastructure.

2. What Should Have Been Done Differently

Team and Collaboration

• Better communication during Iteration 3 could have prevented misunderstandings about API endpoint assignments.
• Increased frequency of check-ins with the customer to align expectations.

Project Development Process

• Breaking down larger use cases would have improved workload distribution, especially for tasks requiring complex integrations.
• Earlier identification of testing requirements could have saved time in Iteration 4.

3. What We Learned

• Technical Skills: Mastery of CI/CD setup, advanced use of Docker containers, Spring Framework, and efficient PowerShell scripting for Active Directory.
• Team Dynamics: Enhanced collaboration strategies, especially in cross-functional teamwork during debugging sessions.
• Time Management: Improved task estimation and adherence to deadlines despite unforeseen challenges.

4. Customer’s Opinion

The customer expressed satisfaction with the final deliverable and plans to use the product for managing Active Directory operations in their organization. They also suggested future enhancements, such as extending API functionality to include audit logging.

---

Role and Responsibilities (Nikita Filin)

As a member of the team, my primary responsibilities included:

CI/CD

• Configured and optimized the CI/CD pipeline using Jenkins to ensure seamless integration and deployment.
• Automated build, test, and deployment processes, reducing manual effort and ensuring faster feedback cycles.
• Addressed and resolved pipeline-related issues, ensuring stability throughout the project lifecycle.

Testing

• Designed and executed unit tests for individual components to ensure functionality met specifications.
• Conducted acceptance testing, validating the system against the defined requirements.
• Documented test results and provided actionable feedback to other team members.

Requirements Development

• Played a key role in gathering, analyzing, and documenting project requirements.

Below you can see Jenkins pipeline interface and my amount of commits.

Role and Responsibilities (Arkadi Statsenko)

As a member of the team, my primary responsibilities included:

• Development of core application functionality.
• Project Management.
• Communication with all parties, including university mentors and the client.
• Peer-review of another project (Digidoc for business).

GitHub statistics:

Role and Responsibilities (Alina Gudkova)

As a member of the team, my primary responsibilities included:

• Outlining the project plan and drafting the product vision.
• Preparing release notes.
• Performing non-functional requirements verification, peer-review response.
• Ensuring the system reflects the functionality outlined in our plan.

Role and Responsibilities (Artemi Sotskov)

As a member of the team, my primary responsibilities included:

• Preparing documentation for the presentations.
• Peer-review response, performing non-functional requirements verification.
• Documentation of the project.
• Testing the application.