BUSINESS OF IT

.docx

School

Western Governors University *

*We aren’t endorsed by this school

Course

Business

Subject

Information Systems

Date

Jan 9, 2024

Type

docx

Pages

5

Uploaded by CommodoreElectron13198

BUSINESS OF IT – APPLICATIONS – C179 Henry Santana Student ID: 011308113 A. Considering Soleil Panel Distribution's rapid expansion and the swift integration of new talent, the linchpin for their future success lies in a robust Information System (IS) solution. Information Systems serve as a pivotal tool for upper management in steering the organization towards its strategic objectives by aggregating data from every tier of the business. This reservoir of data becomes instrumental in decision-making, enabling management to refine existing processes or instigate innovative ones as circumstances dictate. Additionally, IS solutions contributing to elevating quality, amplifying productivity, and enhancing overall profitability (Gunawan, 2022). Incorporating an IS solution not only streamlines the onboarding process for fresh recruits but also positions the company to achieve operational efficiency across the entire spectrum of its business operations. A1. Soleil Panel Distribution is aiming to create a novel software solution, SolDistHr, to fulfill their onboarding requirements. Concurrently, they are looking to tackle security and customer support issues comprehensively. To achieve this objective, the development of the Information System (IS) software should follow the Business Process Management (BPM) approach. BPM can be defined as a specific guiding principle for constructing processes and/or software, with a focus on defining business goals and ensuring the prompt and efficient delivery of top-tier products and services. Moreover, BPM plays a pivotal role in addressing security and customer support concerns by verifying that the new software aligns with industry standards, and all processes and procedures are meticulously documented.
A2. 1) Change Initiation Request – The starting point involves recognizing the need for change, primarily stemming from the outdated orientation process. Within this phase, all relevant details are recorded, covering the reasons for change, potential impacts, implementation timelines, and expected benefits. 2) Change Assessment and Planning – This stage involves the engagement of senior management, who assess the proposed change and conduct thorough risk analyses. A detailed schedule for the change is formulated, along with a fallback plan in case of any complications with the new orientation process software. 3) Approval of Change – Key stakeholders are involved in scrutinizing the proposed change. Based on their evaluations, the change will either be given the green light or rejected. 4) Change Implementation – This phase signifies the development of the orientation process application software. The software undergoes the stages of development, testing, and eventual release into the production environment. 5) Evaluation and Closure – Prior to concluding the change process, a comprehensive review is conducted to ensure that the implementation aligns with the planned objectives. A3. 1) The Administrator plays a crucial role as the primary point of contact for the software team. Drawing from his previous expertise in managing the orientation process, he possesses valuable insights and feedback that can greatly contribute to the development of an advanced and improved software application solution. 2) The Programming Group - Engaging with the administrator, employees, and management, the programming team will analyze the essential criteria for the application. 3) The Executive Leadership - Steering and providing financial support for the project, the management will oversee that the new orientation application adheres to the company's core values and stays within the designated budget. 4) Team Members - They will also offer insights and recommendations on the features and functionalities to be included in the new training software B.
I opt for the Agile development approach. B1. I lean towards the Agile development method due to its ability to release the software incrementally. Given that this project marks the team's first venture into software development, the chosen Agile approach empowers the team to pinpoint and address issues throughout the entire development process, facilitating adaptability. The only drawback lies in its reliance on real-time communication, demanding significant engagement from end users during the development stage. B2. I prefer adopting the Scrum approach within the Agile development method. In Scrum, the development unfolds through short cycles referred to as sprints. The team collaborates collectively, obtaining continuous feedback to achieve specific deliverables rather than completing the entire project in one go. The Scrum framework encompasses three primary roles: the product owner, offering guidance to the team in each sprint; the team (comprising software developers in our context), jointly responsible for the outcomes; and the scrum master, dedicated to overseeing the processes. To kickstart the Scrum process, we establish a vision for the project—specifically, a novel orientation process software application designed to facilitate the swift and efficient onboarding of new talent. Subsequently, we gather all software requirements and essential functionalities from key contributors, documenting them in the Product Backlog. We then prioritize functionalities to be accomplished in each sprint, documenting them in the Sprint Backlog (for instance, sprint 1 – app design). Concurrently, the tasks required for completion are organized on the Scrum Board, outlining team members' assignments as "to do," "busy," or "done." Following this, four crucial meetings are conducted: 1) Sprint Planning meeting, outlining responsibilities, and setting objectives for the ongoing sprint. 2) Daily Standup meeting, ensuring the project aligns with the plan. 3) Review meeting, presenting outcomes and gathering feedback from key contributors. 4) Retrospective meeting, pinpointing areas for enhancement before the initiation of the subsequent sprint.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help