Project Plan

Scope

Iteration 1

1. Product Vision

• Priority: Must-have
• Estimate: 4 hours
• Develop a clear product vision document

2. Functional Requirements & Use Cases

• Priority: Must-have
• High-Level User Stories
  • Estimate: 5 hours
  • Create high-level user stories for core functionalities
• Use Case Specifications
  • Estimate: 5 hours
  • Write detailed use case descriptions for key API functionalities

3. Non-Functional Requirements

• Priority: Must-have
• Estimate: 1 hour
• Define non-functional requirements (e.g., performance, security, scalability)

4. Collaboration Infrastructure

• Priority: Must-have
• Estimate: 4 hours
• Set up Wiki for documentation and GitLab for issue tracking and task management
• Link the issue tracker to use cases and functional requirements

5. Project Plan

• Priority: Must-have
• Estimate: 7 hours
• Define project roles, work processes, and communication methods
• Create and organize tasks in the issue tracker for team members

Iteration 2

1. Core API Design

• Priority: Must-have
• Create REST API for querying user accounts
  • Estimate: 12 hours
  • Design and implement API endpoint for querying AD user accounts
• Implement logic for retrieving user details from AD
  • Estimate: 14 hours
  • Develop backend logic for pulling user details from Active Directory
• Write validation rules for account creation
  • Estimate: 8 hours
  • Validate inputs to ensure valid user account details are processed

2. Application Functionality

• Priority: Must-have
• Implement REST API for creating user accounts in AD
  • Estimate: 12 hours
  • Design API to create new users in AD
• Implement logic for adding users to AD
  • Estimate: 14 hours
  • Develop logic to execute AD commands for adding users
• Design REST API for updating user details in AD
  • Estimate: 12 hours
  • Create the API endpoint for updating user account information
• Implement logic for user detail updates in AD
  • Estimate: 14 hours
  • Build logic for updating AD user information and synchronizing changes

3. Group Management

• Priority: Should-have
• Design REST API for creating groups in AD
  • Estimate: 12 hours
  • Implement API to create groups in AD
• Implement logic for adding groups to AD
  • Estimate: 12 hours
  • Develop PowerShell integration to add groups to AD
• Validation for group creation
  • Estimate: 8 hours
  • Add input validation for creating groups in AD

4. Continuous Integration Setup

• Priority: Must-have
• Estimate: 5 hours
• Automate build and deployment process, ensuring continuous integration works smoothly

5. UI Wireframes/Examples

• Priority: Should-have
• Estimate: 5 hours
• Create detailed input-output examples for key API endpoints

6. Database Design & Integration

• Estimate: 15 hours
• Priority: Must-Have
• Design database schema to support AD command storage
• Implement basic CRUD operations in the database

Iteration 3

1. Complete Core Functionality

• Create REST API for resetting passwords in AD
• Design API for enabling/disabling user accounts
• Implement logic for enabling/disabling user accounts in AD
• Create API for group membership modifications

2. Automated Testing

• Automated Tests for core use cases
• Build testing framework for API and PowerShell execution

Iteration 4

1. Final Functionality & Bug Fixes

• Implement final changes from customer feedback
• Resolve critical and high-priority bugs

2. Testing & Verification

• Internal acceptance testing
• Non-functional requirements verification (e.g., performance, usability)
• Stress-test the application for performance

Project Roles

• Arkadi: Project Manager, Communication Lead, Developer
• Nikita: Developer, Requirements engineer, Documentation manager
• Artemi: Developer, DevOps engineer
• Alina: Developer, Tester

Communication Means

• Client: E-mail
• Task Management, Team Communication: Messenger

Work Process

Tasks and solutions are determined in collaboration with the client. Feedback and tasks completeness are also discussed with the client. Project roles are defined above.