The learning outcome for this unit involves the process of developing an information system (IS) for an organization. There are many factors involved in this process, including core activities and the methodologies for managing the process. Project management plays a part as well. Additionally, IS development does not happen in a silo; there is also the business side to consider as part of the process. All of these considerations are brought together and addressed in this assignment. MBA 5401, Management Information Systems 4 Assignment Instructions: For this assignment, you will need to access the CSU Online Library to research two articles concerning information systems development and project management. Drawing on these two articles, your textbook, and other sources, write an essay that addresses the following: 1. Provide a well-formulated thesis statement in your introduction paragraph. 2. Explain how a business user could be involved in the core activities of building an information system. 3. Analyze how software development methodologies (such as agile development) can work in tandem with project management for the benefit of both information systems development projects and organizations. 4. Evaluate how project managers and/or IT managers can ensure that information system development projects are in alignment with business strategies and goals. 5. Summarize your findings in a five-page paper using proper APA formatting
In this world of Globalization, the importance of Information system has been stressed enough, for the success of the Organisations across the Globe. In earlier days, it has been an advantageous move to have information systems and technology in an organisation. But in today’s millennial world, it is a complaint requirement to be technologically updated. Referendums and regulations like Data Protective directive and GDPR formulations. In today’s world, it is imperative that Organisations adopt technology/ embrace them and build Information systems, which would uplift the growth of the Organisations. Having said that what are the key areas of IS? It is not just a one man or one department’s job to create an IS. It is the collective leadership decision and a collaborative effort with which an effective IS can be built in an organisation. Though an IT departments of IT vendors may actually code it, but it the Leadership which gives the strategic vision, the business that gives the input and direction and it is the end users of the organisations who give the actual needs and wants and the legal which helps to be complaint. Hence it is a collective effort within the organisation to build an effective IS.
Business User’s Role:
It is a Fact that an IT team actually develops and implements an IS along with the help of the Business Analysts. But who do the Business Analysts get the inputs from? It is the Business users. While defining an IS, the Business Analysts, after the Project charter is made, approaches the Business users. They FIRST understand the Needs or the Problem areas from the Business users. They actually sit with the Business users and understand how they work or behave or capture the information. They understand the AS-IS-process.
And if Business user do not co-operate, then the BA’s cannot understand the current scenarios, which might have a major impact in the design of IS. After this aspect then the BA’s come up with a POC/Prototype or the design of the IS and schedule a Brainstorming session with the Business users. The business users would be walked through the design or the solution and their Key inputs would be captured. This is a session which would explain their needs or problem and depict the proposed solution. This would probably be a Demonstration of the future application lookalike or would be. Here without the inputs from Business users the design cannot be approved or completed. And during the next phase of Development, in a Agile way, say Scrum, the Business users or the Business product owners and other Business Stake holders would be Part of the Daily Scrum , Scrum Planning, Backlog identification and Prioritization as well as demo. Hence at every level the Input of Business users are very crucial.
Agile way of Development in PM:
The concept of agile is working flexibly, as per the available requirements, building piece by piece, and showcasing small piece of developments very frequently.
The concept of agile let us take the Scrum Methodology of the SDLC. Here in the Scrum Methodology, it starts with Sprint Planning. Here the product Owner , the scrum master, BA and team members meet for the first time and identify requirements that needs to be developed. They identify the requirements in pieces or functional points. These are kept as Product backlog. The Product owner identifies the priority as to which item, to go for Development first and as well answers all the queries with respect to that requirement. The scrum master plans for the sprint, which typically are two weeks. They pick up items which need to be developed in the next two weeks, which would also be showcased to the business, showing them progress in development style, like showcasing the working piece of development.
In this agile method, the sprint planning happens as per the Project Management Plan. The Project management plan being prepared by the PMO or the Project Manager would be the base for defining and achieving the milestones. Every milestone that is there in the PM plan would be absorbed and the Sprint planning would be created based on that. This will ensure that the idea of creating an INFO SYSTEM is proceeding as per the project management plan and helps achieve the goal. It also helps the organisation, in form of , being agile, the leadership and the business is able to see Developed and working piece of code as frequent as a couple of weeks. In this way they are able to track the progress very easily and frequently as well have sufficient space to do any changes or modification as and when required and with minimal change in efforts. This also helps organization keep track of its vision and strategic directives. This way the PM plan created is being used to achieve the goals in an agile way and also enables the Organisation to track the progress as well as reaps the benefits or realize the benefits in a larger and efficient way.
PM tracking of Goals:
As explained earlier, the agile methodology (Read as Scrum, in this case) could be based out of the Project Management plan created. Using the Project plan created, the Project or the IT manager can use the requirements, deliverable their Milestones and efforts defined to start the Scrum methodology. The Scrum planning can be called by the Product Owner (PM/IT Manager can act as Product Owner, if they perform the role) and all the requirements from the PM plan can be used to create the Product backlog which would be the base to define the sprint planning and the sprint sessions. By using the PM plan, the sprints can be planned and deliverable can be achieved. Any change in Business strategies will have an impact on the PM plan. And any change to the PM plan would be accommodated in the Sprint planning and subsequent sprint development cycles. So for example there is a likely change in the business strategy, like to change the way a set of data is to be captured, arising out of some legal compliance, the same can be updated in the PM plan. The PM or the IT manager can take cognizance of the same the same changes can be prioritized in the sprint planning, picking that change from the product backlog and delivered as per the change in the Business strategy. The business goals can be achieved via the milestones I the PM plan and can be tracked in the scrum deliverable methodology.
To sum up, the Information system, which would, obviously be developed by the IT team, but the co-operation of business, collaboration of different departments, vision of leadership and directions from Business and inputs from business users are very crucial in how the Information system is being shaped in the Organisation.
The Development Methodology , Scrum, which is one of the Agile methodology helps the project managers or the IT managers, manage the Information system development as pr the defined PM plan, track the milestones, progress and showcase the progress very frequently and easily handle any changes to the business strategies as well as ensure the goals of the business are met.