The Library's seeks to develop a comprehensive inventory tracking system to enhance its inventory control process.

The proposed inventory tracking system aims to facilitate the annual inventory check, wherein staff members will manually go through each section and room within the Library to verify the presence of items against the master inventory list. The system will offer the following functionalities:

Master Inventory List: Maintain and update a central database containing detailed records of all library resources.

Room$/$Section Inventory: Organize inventory lists based on different sections or spaces within the Library to streamline the search and verification process.

Resource Allocation: Generate reports indicating which resources should be available in each designated area.

Physical Inventory Update: Enable staff to manually update the inventory list during the physical inventory check, marking items as "found" or "not found."

Reporting Tools: Generate reports to analyze inventory data, track trends, and identify discrepancies.

The system will support file imports and exports in formats like $.$xls$,.$xlsx$,$ and $.$csv$,$ ensuring seamless integration with the existing inventory management system used by the Library.

Though the system won't be an app with barcode scanning capabilities, it will provide an efficient and reliable means to manage the Library's inventory. By implementing this system, Library aims to maintain an accurate and up$-$to$-$date list, leading to better resource utilization and an improved experience for library users in the community.

$1.$ Review the project requirements for the Library Inventory Tracking System. Identify key stakeholders and their expectations.

$2.$ Write down a list of questions that need to be addressed during a discussion with the stakeholders to gather additional insights and requirements. Minimum $5$ questions.

$3.$ Choose Agile style as the preferred process model for this project and justify your decision.

$4.$ Set up a communication plan to ensure effective communication among team members and stakeholders.

$5.$ Break down the requirements into smaller, manageable user stories or tasks.

$6.$ Prioritize the user stories based on their importance and complexity.

$7.$ Develop an initial prototype of the CIAT Library Inventory Tracking System using a rapid prototyping approach.

$8.$ Conduct a review session with stakeholders to gather feedback on the prototype and make necessary adjustments.

$9.$ Identify potential risks that may arise during the development process.

$10.$ Develop a risk management plan with mitigation strategies for each identified risk.

$11.$ Hold regular stand$-$up meetings to discuss progress, challenges, and plans for the day to embrace changes in requirements and demonstrate the flexibility to adapt the prototype accordingly.

$12.$ Monitor the project progress regularly to prevent scope creep and ensure the system stays aligned with the requirements.