Organizational Structure for Application Development

1. Organizational Structure for Application Development Presented BY: Vladan Bogdan

2. Presentation outline Define software development organizational structure 2. Outline Dimensions of an IT Organization 3. IT Organizational Structures TYPES 4. Distribution of job duties

3. Define software development organizational structure organizational structure: consists of activities such as task allocation, coordination and supervision, which are directed towards the achievement of organizational aims. Software development organizational structure: Consists of IT roles, responsibilities, skills and budgets that focus on projects that address specific business activities.

4. Outline Dimensions of an IT Organization People Each individual in an organization has certain skills, and these skills are typically measured against formal or informal performance metrics. Process The procedures and methodologies used by people in the organization. Technology The specific skills and tools that people in the organization use to carry out the business functions of the organization. structure determines the manner and extent to which roles, power, and responsibilities are delegated, controlled, and coordinated, and how information flows between levels of management.

5. IT Organizational Structures TYPES Project-Centered: In such an organization, each group is primarily self-sufficient and is staffed by enough skilled developers to address every stage of the development lifecycle. Department-Centered: Department-centered development organizations start to become practical as a group grows above 25 developers. At these staffing levels, there are sufficient people to form multiple departments centered on particular software skills or lifecycle areas. Matrix Organization: Matrix organizations are sometimes used in companies with a large number of software developers working on a broad array of software projects. Product Line Organizations In a product line organization, developers are organized into projects based on business product lines as opposed to skill set departments. For instance, one product line might have requirements analysts, OS experts, some web developers, and configuration management.

6. Distribution of job duties Software development director: plans the direction and oversees the operation of software development organizations. Lead software architect: technical lead on the project and, from a technical perspective, ultimately carries the responsibility for the success or failure of the project. project manager have the responsibility of the planning, execution, and closing of any project. systems analyst researches problems, plans solutions, recommends software and systems, and coordinates development to meet business or other requirements.

7. Distribution of job duties Development Lead: Focuses on providing details to the lead software architect and is the first line of support for the developers. Quality Assurance: Responsible for ensuring the quality of the solution and that it fits in to the requirements gathered by the systems analyst. Developer: Developer actually writes the code for the specifications provided by the Development Lead. Tester: creates the Test documents from the Plans and Scripts created by the QA.

8. Roles comparison • SOFTWARE DEVELOPERS DEFINE REQUIREMENTS, DESIGN AND IMPLEMENT THE PRODUCT, AND MINIMALLY VERIFY THE PRODUCT MEETS REQUIREMENTS. • SOFTWARE QUALITY ASSURANCE PEOPLE, THE PRODUCT VERIFIERS, DEFINE PRODUCT TEST REQUIREMENTS; DESIGN, IMPLEMENT AND VERIFY THE TESTS; VERIFY THE PRODUCT MEETS THE REQUIREMENTS.

9. Organizational Structure Issues Combining software development and operations into a single organization Organizing software technology specialists by project Organizing software technology specialists by APPLICATION DOMAIN Organizing software DEVELOPERS BY DELIVERY PLATFORM (Unix, windows, mainframe…) Separating software development and software maintenance groups Representing projects in the formal organizational structure instead of defining project teams that cut across organizational boundaries Organizing software developers into long-term and short-term development groups

10. Organizational Structure IssuesContinued Designing organizations that need "super-developers" to succeed Designing organizations that tolerate underachievers Designing organizations that reward empire building Setting organizational goals that compete against each other for customer satisfaction Organizing around individuals instead of personality types Mandating organizational changes from the top down

11. Summary of organizational measures