MGMT8086 - Agile Principles Assignment PDF

MGMT8086 - Agile Principles Assignment \#1 Team Member 1: Nikilesh Kumar Mandla Student \#: 8999813 Team Member 2: Venkataraja Reddy Student \#: 9030717 Team Member 3: Karthik Mediboina Student \#: 9041463 Question 1A: - I would suggest that the incremental life cycle model is best...

MGMT8086 - Agile Principles Assignment \#1 Team Member 1: Nikilesh Kumar Mandla Student \#: 8999813 Team Member 2: Venkataraja Reddy Student \#: 9030717 Team Member 3: Karthik Mediboina Student \#: 9041463 Question 1A: - I would suggest that the incremental life cycle model is best suitable for the Alpha beverage company to move from Expenso Tech to a new software platform that is an in-house ERP system because the annual cost for the current software Expenso Tech is charging double the amount for each year. - By using the process of incremental life cycle the company can manage and can introduce more efficient ways for the system and can manage and use time effectively step by step not wasting time on waiting for the entire system to get ready. - Incremental features are very efficient and easy to implement and also easy to use the specified features. As the entire system of the Expenso system is not released at a time but they are gradually released in smaller batches by developing each of the parts and also by testing it entirely and implementing it main inputs, specifications, and features very efficiently and fast. So that will not be more dependent on Expenso Tech and can use more of its specifications for a seamless and also effective way of moving to better management. - It really helps Alpha Beverages to maintain the sustainability of the organization as the modules of it is developed in smaller batches and in a separate way so that the organization can use these systems before they move from existing software and also it helps the staff members to use this system very easily. **Why Choose Incremental Lifecycle?** **Earliest Adoption & Features Usage Early** - Here with this process, the independent modules built can already be put into practical use by the Alpha Beverage company when all the implementation cannot be considered complete. - This is going to result in no business disruption due to the gradual adaptation of staff to the change. **Less Risks & Adaptability** - Any issues that do crop up are fixed piecemeal and without causing a complete and costly collapse. - Feedback from one stage helps to perfect the next module to make the system firmer for real business out in the field. **Cost-Effective & Scalable Solution** - Instead of one large upfront investment, the cost of the project is distributed over time. - New features & enhancements can be added as business needs evolve. Question 1B: **1.Faster Adoption and Business Continuity** - This will also allow the firm to begin taking control of the vendors and processing orders while other parts of the system are in development. - Training is easier and more effective since employees do not have to learn everything at once. **2️. Lower risks and early problem detection** - Smaller pieces can show problems that can be fixed rather than having expensive failures later. - This helps in reducing last-minute surprises. **3️. Flexibility for Future Improvements:** - Alpha Beverage can change the features in relation to feedback provided by the users. More functionalities can be added if further business needs arise without disrupting the whole system. Question 2: **1^st^ Phase (Project Kickoff & Assessment)** **July 2024 -- August 2024** **Goals:** - Specifying the requirements, analyzing their importance and sorting them. - Preparing business requirements documents and **Action items:** - **Gathering requirements:** Collaborate with clients and find out what is most needed and better to have in the scope. - **Stakeholder Collaboration:** Conducting workshops with stakeholders who are important users of the product to get clear inputs. - **Risk & Cost Analysis:** Evaluate the risks and cost considerations. - **Development Plan:** Specify **the** product incremental development plan and its timelines. **The outcome of this Phase:** - The analysis and project outline - High-level plan and specification - Development & execution plan **2^nd^ Phase Architecture and System Configuration:** **September 2024 -- December 2024** **Objectives:** - Defining architecture, database configuration, and setup. - Setting technical standards for incremental development approach. **Activities:** - **Architecture Design:** Define configuration, integration, and flows. - **Prototypes Building:** Build wireframes for the development of user interfaces. **Deliverables:** - Suitable technical Stack - System Architecture design - Building prototypes and wireframes for user interfaces **3^rd^ Phase Incremental Development, testing and deployment** **timeline January 2025 -- July 2025** Each increment cycle will deliver a fully functional module to ensure continuous usability. **Increment 1** Acquisition Module**:** Timeline **November 2024 -- February 2025** - Order tracking, and supply chain management flow. - Invoices & cost tracking. **Increment 2** Production planning for sales & order management: Timeline **March 2025 -- July 2025** - Real-time sales analytics. - Implementing RBA (role-based access) control, and auditing. - Integrate all developments. - Final testing for quality assurance. **Activities:** - Sprint plan & execution - Testing and bug fixes **Deliverables:** - Incremental software releases. - Testing & feedback - Bug fixes and optimizations. **4^th^ Phase** Deployment & Documentation: Timeline August 2025 -- September 2025 **Objectives:** - Ensure smooth and uneven production flow. - Final refactoring before production goes live. **Activities:** - Data migration from the previous platform to the new go-live platform. - System documentation and training. **Deliverables:** - Final production live ERP system - Documentation and training - Post-production monitoring and support. All the phases ensure to build a product that obeys agile principles of continuous delivery and feedback from the clients even in late development. Question 3: **Regular sprint reviews**: This type of meeting is something we aim to arrange with the most important people from procurement, production, sales, top management, and IT. Later, we will brief them on a regular stakeholder sprint review which will be our exhibition of what was done and then there will be time for them to give us their feedback; only after that we can agree on the next feature focus development in between each sprint. With this, the involvement of everybody is guaranteed and in this way, the positives and the negatives for all concerned parties will be tackled. **Cross-functional workshop:** Multi-Departmental Workshops One of the events also consists of the launching of the next sprints through cross-functional workshops involving all the divisions in the requirement definition and the features\' prioritization. The joining of all stakeholders in this stage will make sure that different points of view are perceived as success elements of the project ownership and collaboration ideas. **Transparent Communication channel**: Information Sharing An open communication channel is being developed on which we transmit matters like grim progress, challenges, and milestones. The implementation of information technology would be a good example of a project management tool. All involved parties, particularly facility managers and operational staff, would be given a chance to have a look at all the matters that are bugging us Question 4: Features of Alpha Beverage's internal ERP system The three primary business domains that emphasize for ERP solutions: Sales & Order Management, Production, and Procurement. There will be at least four essential components in every department. 1. Department of Procurement - **Management Supplier**: Maintain a record of supplier information, terms of contract, and evaluating performance. - **Purchase Order of Management (PO):** Draft, authorize, and purchase orders monitoring. - **Demand forecasting & inventory supply restocking**: Suggesting reordering and auto-stock tracking. 2. Management of production & inventory: - Work order Management & bill of materials: - Plan & Production scheduling: Make the most of production runs by considering demand, labor limits, and materials availability. 3. Orders & Sales Management: - Order processing for customers: Monitoring orders from placing to completion - Dynamic pricing & discount management: Control pricing based on promotions and offers and seasonality. - Returns & refund processing: Manage product returns, refunds, and logistics for restocking. Two proposals for feature prioritization are: **Proposal 1**: Business-Critical First This method ensures that most tasks continue without any deviations or delays before ExpensoTech support ends. 1^st^ phase -- Order Management and procurement (Assures trust and business continuity) 2^nd^ phase -- Inventory Managing and goods production 3^rd^ phase(Final) -- Forecasting trends and performance analytics Pros: This guarantees execution stability, avoids any bottleneck situations, and assures required functions are ready on time. Cons: Refactoring and Advanced analytics may delayed as they are time-consuming. **Proposal 2**: Incremental Minimum Viable Product Developing basic viable product with basic essential functionalities for each department and plan for incremental enhancement. - 1^st^ phase -- Basic feature availability for product and order processing, order managing and tracking inventory items. - 2^nd^ phase -- Extend to performance analytics of the suppliers, product forecast analysis and client insights. - 3^rd^ phase -- Automation and optimizations. Pros: Users get early product delivery which is working and allows them to give faster feedback which drives the next implementations. Cons: The process may start with basic functionalities and broaden its scope after final delivery. Question 5: **Parallel System Deployment Strategy: -** - To minimize the risks of transition from ExpensoTech to the new ERP system, a parallel deployment approach is recommended where: - The new ERP runs in parallel with ExpensoTech for the first 6 months to make sure everything is running smoothly. - Employees will gradually shift to the new system but also refer back to the old system for backup purposes. - Once confirmed that stability, ExpensoTech will be completely phased out. References