Choose A Relatively Small Organization That's Just Beginning

Choose A Relatively Small Organization That Is Just Beginning To Us

Choose a relatively small organization that is just beginning to use information systems. What types of systems are being used? For what purposes? To what extent are these systems integrated with each other? With systems outside the organization? How are these systems developed and controlled? Who is involved in systems development, use, and control?

Use the Web to find out more about the Agile Methodologies. Write a report on what the movement toward agility means for the future of systems analysis and design.

You may want to keep a personal journal of ideas and observations about systems analysis and design while you are studying this book. Use this journal to record comments you hear, summaries of news stories or professional articles you read, original ideas or hypotheses you create, and questions that require further analysis. Keep your eyes and ears open for anything related to systems analysis and design. Your instructor may ask you to turn in a copy of your journal from time to time in order to provide feedback and reactions. The journal is an unstructured set of personal notes that will supplement your class notes and can stimulate you to think beyond the topics covered within the time limitations of most courses.

Paper For Above instruction

Choose A Relatively Small Organization That Is Just Beginning To Us

Small organizations, often characterized by their limited resources and narrow operational scope, are increasingly beginning to adopt information systems to streamline their processes, improve efficiency, and enhance decision-making capabilities. An exemplary case is a small regional retail store, which I will refer to as "Sunshine Retail," that recently started integrating information technology into its operations. The introduction of digital systems was motivated by competitive pressures, customer demand for convenience, and the need to manage inventory more efficiently.

Types and Purposes of Systems Used

Sunshine Retail initially implemented several basic information systems. These included point-of-sale (POS) systems that facilitate transaction processing and inventory management. The POS software automates sales recording and stock updates, reducing manual errors and providing real-time sales data. Additionally, the store has begun using a simple customer relationship management (CRM) system to track customer preferences and purchase histories, aiming to enhance personalized marketing efforts and customer loyalty.

Other systems involve accounting software to handle financial transactions, payroll, and expense tracking. The primary purpose of these systems is to improve operational efficiency, accuracy in record-keeping, and data accessibility. By automating routine tasks, Sunshine Retail staff can focus more on customer service and strategic planning rather than manual bookkeeping.

System Integration and External Connections

Given the small scale of Sunshine Retail, the systems are relatively independent at this stage. While POS and accounting systems operate separately, they are capable of data export and import, providing some level of integration. However, there is limited real-time data sharing or fully integrated enterprise resource planning (ERP) systems. The CRM system is somewhat isolated but is planned to be integrated with sales data for more comprehensive customer insights.

External connectivity is limited mainly to supplier communication via email and basic online ordering portals. There is minimal integration with external systems, primarily due to resource constraints and the organization's nascent stage of digital adoption. As the organization expands, more sophisticated integration with external supply chain systems and logistics providers might be considered to improve operational flow.

Development and Control of Systems

The current systems were primarily purchased from commercial vendors, with Sunshine Retail's owner and a hired IT consultant overseeing the deployment. The owner makes key decisions on system upgrades and new implementations, while the IT consultant handles daily system maintenance and user training. System control is primarily maintained through administrative privileges assigned to the owner and designated staff members who handle routine tasks.

As the small organization grows, there are plans to develop custom systems tailored to specific needs. System development is likely to involve external vendors or software developers, with the owner and IT consultant remaining the primary controllers to ensure alignment with business goals. Data security and system integrity are managed through basic password protections and regular backups, but formal policies are still in development.

Impact of Agile Methodologies on Systems Analysis and Design

The agile movement emphasizes flexibility, customer collaboration, and iterative development, contrasting with traditional waterfall models. Agile methodologies encourage small, incremental releases, continuous feedback, and adaptability to changing requirements. For small organizations like Sunshine Retail, adopting agile practices can significantly influence systems analysis and design processes.

In the future, systems analysis will become more collaborative and less linear, with project teams comprising cross-functional members, including non-technical staff. The emphasis will be on delivering functional prototypes rapidly, which allows organizations to adjust their systems according to evolving needs and market conditions. Agile approaches facilitate rapid deployment of small system components, reducing risks associated with large-scale, monolithic projects.

Moreover, agile methods foster a mindset of continuous improvement, where feedback loops enable ongoing refinement of systems, making them more aligned with operational realities. For small organizations, this adaptive approach offers a competitive advantage, enabling quick responses to market trends and customer demands.

The shift towards agility also impacts system documentation and planning. Instead of extensive upfront specifications, documentation becomes lightweight, focusing on user stories and acceptance criteria. This approach streamlines communication and reduces delays caused by misaligned expectations, making the systems development process more efficient and responsive.

In conclusion, the movement towards agility signifies a paradigm shift in systems analysis and design, emphasizing iterative development, collaboration, and flexibility. For small organizations starting with limited resources, agile methodologies provide a practical framework to implement systems incrementally, adapt to changes, and deliver value more swiftly. As technology and organizational practices evolve, embracing agility will likely become essential for effective systems management and competitive advantage.

References

• Conforto, E., Salum, F., Amaral, D. C., da Silva, S. L., & de Almeida, L. F. M. (2016). Can Agile Project Management Be Adopted by Industries Other Than Software Development? Innovation & Management Review, 13(3), 18-29.
• Highsmith, J. (2002). Agile Software Development Ecosystems. Addison-Wesley.
• Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall.
• Stellman, A., & Griffith, G. (2010). Head First Agile. O'Reilly Media.
• Boer, H., & Holsapple, C. (2014). Agile in Healthcare: Moving Toward a More Responsive System. Journal of Medical Systems, 38(3), 232.
• Preston, J. (2017). The Future of Agile Systems Development. IEEE Software, 34(2), 77-81.
• Rigby, D. K., Sutherland, J., & Takeuchi, H. (2016). Embracing Agile. Harvard Business Review, 94(5), 40-50.
• Beck, K., et al. (2001). Manifesto for Agile Software Development. Agile Alliance.
• Ambler, S. (2012). Introduction to Agile Methodologies. Agile Modeling.
• Lenard, H. G. (2019). The Evolution of Agile in Small and Medium Enterprises. Journal of Systems and Software, 157, 110-121.