Project_Management

Scenario:

In the following scenario, you will become the Project Manager, Business Analyst and Systems Architect. Read the transcript from your meeting and complete the tasks for each role. You are not limited to the list of requirements listed here. You need to add new requirements specially the core functionality of the system.

 

Actors:

 

Stakeholder A (Prioritizes the libraries)

Stakeholder B (Prioritizes the bookstores)

Stakeholder C (Both libraries and bookstores have equal priority)

Vendor Project Manager (John)

Vendor Business Analyst (Jen)

Vendor Systems Architect (Jun)

 

Transcript:

 

Attendees:

 

• Stakeholder A (SA)

• Stakeholder B (SB)

• Stakeholder C (SC)

• Vendor Project Manager (John)

• Vendor Business Analyst (Jen)

• Vendor Systems Architect (Jun)

• Vendor Secretary (You)

 

 

Meeting Topic: Unified Library & Bookstore Management System

 

 

John: Alright, everyone, welcome! Today we'll be discussing your vision for this unified management system.

 

SA: Wonderful! First things first, our top priority is streamlining library cataloging. We need a robust system that can handle a vast amount of data across different languages and formats.

 

SB: Agreed. But let's not forget searchability! Customers need to easily find what they're looking for, whether it's a specific book or a genre.

 

Jen: (Makes notes) Excellent points. Can you elaborate on the data formats you envision, Stakeholder A?

 

SA: Absolutely. Ebooks, audiobooks, even physical media with detailed information like ISBNs and publication dates.

 

SC: Hold on, while a unified catalog is important, don't we also need a strong inventory management system? Tracking stock levels for both libraries and bookstores is crucial.

 

SB: (Scoffs) Inventory? Libraries lend books, Stakeholder C. We need a system for circulation and patron management.

 

SA: (Talks over SB) Exactly! Borrowing periods, due date reminders, hold lists - these are all essential library functionalities.

 

John: (Raises hand) Perhaps we can break this down further. Stakeholder A, Stakeholder C, could you elaborate on your preferred functionalities for libraries specifically? Stakeholder B, what about bookstores?

 

SC: Sure. For libraries, in addition to the catalogue, we need features like automated renewals and overdue fines management.

 

SA: Yes, and interlibrary loan integration would be fantastic!

 

SB: (Sighs) Meanwhile, bookstores need functionalities like point-of-sale systems, loyalty programs, and vendor management.

 

Jun: (Whispers to John) This is getting complicated. Conflicting priorities between libraries and bookstores.

 

John: (Clears throat) Stakeholder B, that's an interesting point. Would those functionalities integrate with the library system somehow?

 

SB: Ideally, yes. We want a seamless experience for customers who might browse in a bookstore and then borrow a book from the library.

 

SC: Exactly! A unified system would allow customers to see library availability directly in the bookstore, and vice versa.

 

SA: (Grumbles) As long as it prioritizes library functions.

 

Jen: (Looks overwhelmed) Okay, so we have a lot to consider here. A unified catalog with diverse data formats, separate functionalities for libraries and bookstores, with potential integration points...

 

John: (Nods) Yes, Jen. We'll need to carefully map out the requirements and prioritize based on stakeholder needs.

 

SC: And don't forget user interface design! The system needs to be user-friendly for both staff and patrons.

 

SB: Absolutely. A clean interface with multilingual support is a must.

 

John: Excellent points. We'll make sure user interface and accessibility are addressed in the design phase.

 

 

Summary of Additional Discussion Points

 

Security

• Stakeholder concerns likely revolved around data security for both libraries (patron information, borrowing history) and bookstores (financial transactions, customer loyalty data).

• Possible discussion points:

  • Encryption standards for data storage and transmission

  • User authentication and access control levels

  • Disaster recovery and backup plan

 

Reporting

• Stakeholders likely have different reporting needs for libraries and bookstores.

• Possible discussion points:

  • Libraries: reports on borrowing trends, overdue fines, interlibrary loan activity

  • Bookstores: sales reports, inventory management reports, customer loyalty program analytics

  • Reporting formats (e.g., charts, dashboards) and delivery methods (e.g., email, automated reports)

 

Other Functionalities

• The transcript hints at potential discussions around:

  • Integrations with existing library and bookstore systems

  • User management features (adding new staff/patrons, managing roles and permissions)

  • Mobile app development for customer self-service

 

Unresolved Issues

• The core conflict between Stakeholder A (prioritizes libraries) and Stakeholder B (prioritizes bookstores) remains unresolved.

• This will need to be addressed during the requirements gathering and prioritization phase.

 

 Type yes once done reading

HERE you are a Project Manager

Given the scenario above, how many stories would have been created? Why?

Show me the process on how you will build the project timeline. Provide links to additional documents if needed.

Based on your timeline and Jen's output, how will you estimate the project cost? Show me the process. Include links to additional documents if needed.

You have completed the first quarter of the project when a new Stakeholder joined the team/discussion. Due to a bad experience of this stakeholder with your company in a prior engagement, the stakeholder wants you to complete the project with half the time needed (e.g. you originally estimated that the project will be completed in 12 months. On your end of 3rd month/1st day of 4th month, this stakeholder wants you to complete the whole project by the 6th month. Meaning you have the 4th, 5th, 6th month to complete the project.) This stakeholder said that this is non-negotiable and should you fail to comply, the penalties that were stated in the contract will take effect, making your company go bankrupt. Detail below what will you do.

With the shortened timeline, how will you ensure that the project will be completed successfully? Detail below

In another universe where question number 5 did not happen, a new stakeholder joined and demanded (on the start of the 4th month) that the project budget be cut in half. E.g. the original budget of 15M, What/how will you shift your resoures to accomodate the change?

Both question 5 nd 7 are quite heavy oriented questions. Have a breather here. Type I'm alive again!

Let go to another universe where 5 and 7 did not happend. However, your senior developer resigned. This is followed by a mass exodus of other developers. How will you ensure timely delivery?