IS Strategy, Planning, and Project Management

Information Systems (IS) are crucial for modern organizations. Understanding IS Strategy, Planning, and Project Management is essential for students and professionals alike to navigate the complexities of digital transformation. This guide will break down how IT investments are strategized, planned, and managed from conception to ongoing maintenance, ensuring they align with business objectives and deliver value. We'll explore different project methodologies, key success indicators, and the roles involved in successful IS development.

IS Strategy: Laying the Foundation for Digital Success

Organizations must invest in IT/IS from a strategic business perspective to prioritize adequate investments. This approach ensures that digital initiatives directly support overarching business goals.

Origins of New IS/IT Initiatives

New IS/IT initiatives primarily stem from two sources:

1. Business and Digital Strategy: This is the main source, emphasizing strategic alignment.
2. Development Requests: Employees or external factors identify problems or improvements.

Strategic Alignment: Connecting IT with Business Goals

Strategic alignment is fundamental for proper IS/IT management. It ensures that investments support business strategy and goals, driving new information system development projects.

There are two levels of strategic alignment:

• Basic Level: The IS plan is an outcome of the strategic business plan, where IT acts as a tool to support the business.
• Advanced Level: IT becomes an integral part of the business strategy itself. Technology helps design the business model, and data, digital processes, and IS are key to creating business value.

IS/IT Development Requests: Identifying Needs and Improvements

Employees often notice opportunities for system improvements. A well-organized IS/IT management system provides communication channels to identify these inefficiencies. Requests can come from various user types:

• Departmental users: Focus on operational requests within their department.
• General or functional managers: Have a broader view, submitting tactical or strategic requests that may affect several departments.
• IS Managers / CIO: May request improvements directly or through other groups.
• The environment: External factors like new legislation, customers, suppliers, government, or head office can trigger requests.

Development requests should be comprehensive, including:

1. Identification of the applicant.
2. Detailed description of the problem or improvement.
3. Relevance of the application in the applicant's opinion.
4. Identification of possible solutions (if known).
5. Expected benefits or business value.
6. Users or groups who may be affected.

The IS Committee is responsible for ensuring these communication channels are open and continuously used.

The IS Plan: Your Digital Roadmap

IT investments are significant and impact the entire business. Therefore, any modification or launch of a new IT project requires management approval. An IS Plan is a formalized IS/IT management tool that details all digital projects to be developed or implemented within a specific period. It guides an organization's digital evolution, detailing investment projects that align with business objectives. Its absence can lead to inconsistent investments that fail to address priority needs.

Preconditions for the Development of an IS Plan

Three conditions are essential before developing an IS Plan:

1. Creation of an IS Committee: This multidisciplinary team (management, IT managers, work team) creates, manages, supports implementation, and monitors the IS Plan. Management defines its roles and reporting structure.
2. Strategic Reflection on IT/IS and Identification of Development Lines: Before planning, it's crucial to combine business strategy with how digital technology can leverage it. This involves:

• IS diagnosis: Evaluating the current digital situation.
• IT foresight: Identifying future technology opportunities (technology roadmapping).
• Strategic reflection of the business: Having a clear strategic vision for the period.
• Identifying IT priorities: Combining analyses to decide on the most important IT projects.

3. Budget and Approval Process: Establishing the budget, procedures, and plans for the plan's definition and approval by management.

IS Plan Development Phases

Once preconditions are met, the IS Committee prepares the IS Plan. The plan defines objectives, digital projects, deadlines, resources (people and money), and organizational changes. The management committee then approves it.

The development process typically follows 10 stages:

1. Identify strategic IT/IS challenges: These challenges guide future IT projects.
2. Preliminary list of IT/IS investment proposals: Proposals are generated based on challenges and submitted by different areas. The IS committee screens these.
3. Understand and discuss proposals: Information is verified with business managers, proposers, and other stakeholders. Objectives and scope are clarified, leading to proposals being discarded, added, or merged.
4. Define evaluation criteria: Since resources are limited, the IS committee sets criteria to prioritize the most relevant projects.
5. Apply evaluation criteria: Each project is evaluated against the defined criteria.
6. Rank projects: Projects with low contribution may be discarded. If many compete, criteria are weighted.
7. Review ranking with business managers: Adjustments may occur due to new information, potentially changing project order, leading to a definitive list.
8. Technical, operational, and economic feasibility: Each project is assessed for:

• Operational feasibility: Real need, no undesired effects, user support.
• Technical feasibility: Available, accessible, and maintainable technology.
• Economic feasibility: Benefits justify costs (also considering costs of not proceeding).

9. Detail each project and prepare the plan: This includes project description, strategic importance, deadlines, responsibilities, resources, and value indicators.
10. Approval and communication: Management approves the IS plan. Communicating both approved and unapproved projects is crucial for employee motivation and future participation.

IS Project Management Methodologies

Once an IS Plan is approved, companies choose how to develop planned projects. This involves deciding who develops the system (in-house, subcontracting, outsourcing, crowdsourcing), the development methodology, the type of software (standard vs. customized, proprietary vs. free/open-source), and where the system resides (on-premises, cloud computing).

Understanding Life-Cycle Approaches

The life-cycle approach assumes an information system has a life similar to an organism, progressing through formal stages: analysis, design, build, test, and maintain. Each phase must be completed and formally approved before proceeding. This approach is structured, organized, and suitable for medium to large projects with clear documentation and planning.

Advantages of Life-Cycle Approaches:

• Structured and organized development.
• Suitable for medium to large projects.
• Clear documentation and planning.

Disadvantages of Life-Cycle Approaches:

• Can be slow and costly.
• Requires extensive documentation.
• Very rigid, making changes difficult once development starts.
• Best when requirements are stable from the beginning.

Waterfall Approach (Cascading Life-Cycle)

This is a strict life-cycle approach where phases follow a strict sequence, and no phase can be skipped. Changes are difficult once a phase is complete. It works best when requirements are clear and stable, and the project is well-defined from the start.

Spiral Life-Cycle Approach (Flexible)

More flexible than Waterfall, this approach allows revisiting previous phases and introducing modifications, increasing adaptability during development.

Agile Methodology: Flexibility in Development

Agile methodologies offer more flexible development approaches. Instead of defining everything upfront, requirements and solutions evolve incrementally throughout the project. Examples include prototyping, Scrum, and agile development.

Development occurs in small improvements over time. Projects require interdisciplinary teams (business and technical profiles) working together in shared decision-making. Agile gained popularity after the Agile Manifesto in 2001 and is widely used, especially in web environments, due to its agility and versatility. However, for back-office systems, companies often prefer more robust and reliable systems.

Agile development often divides projects into