Please enable JavaScript.

Coggle requires JavaScript to display documents.

The Managment Spectrum - Coggle Diagram

- - - - Developers
        
        • Difficulty of the problem to be solved
        
        • “Size” of the resultant program(s) in lines of code or function points
        
        • Time that the team will stay together (team lifetime)
        
        • Degree to which the problem can be modularized
        
        • Required quality and reliability of the system to be built
        
        • Rigidity of the delivery date
        
        • Degree of sociability (communication) required for the project
    - - Many agile process models (e.g., Scrum) give the agile team significant autonomy to make the project management and technical decisions required to get the job done.
    - - is a people-intensive activity, and for this reason, competent
        practitioners often make poor team leaders.
        
        Organization
        
        The ability to mold existing processes (or invent new ones)
        that will enable the initial concept to be translated into a final product.
        
        Motivation
        
        The ability to encourage (by “push or pull”) technical people to
        produce to their best ability.
        
        Ideas or Innovation
        
        The ability to encourage people to create and feel creative even when they must work within bounds established for a particular software product or application.
        
        Problem Solving
        
        An effective software project manager can diagnose the
        technical and organizational issues that are most relevant,
        
        Managerial Identity
        
        A good project manager must take charge of the
        project.
        
        Achievement
        
        A good project manager must take charge of the
        project.
        
        Influence and Team Building
        
        An effective project manager must be able to “read” people.
    - - To deal with them effectively, you must establish effective methods for coordinating the people who do the work.
    - - Practitioners
        
        who deliver the technical skills that are necessary to engineer a
        product or application.
      - Customers
        
        who specify the requirements for the software to be engineered
        and other stakeholders who have a peripheral interest in the outcome.
      - Project (thecnical) Managers
        
        managers who must plan, motivate, organize, and control
        the practitioners who do software work.
      - End User
        
        who interact with the software once it is released for production use.
      - Senior Managment
        
        who define the business issues that often have a significant
        influence on the project.
- - - - For a software project, progress is tracked as work products (e.g., models, source code, sets of test cases)
    - - In essence, the decisions of the project manager and the software team should be to “keep it simple.”
    - - To maintain momentum, the project manager must provide incentives to keep turnover of personnel to an absolute minimum,
    - - Establish a consistent mechanism for extracting lessons learned for each project.
    - - This is accomplished by working hard (very hard) to understand the problem that is to be solved and then setting realistic objectives and expectations for everyone who will be involved in the project.
- - - - Project planning begins with the melding of the product and the process. Each function to be engineered by your team must pass through the set of framework activities that have been defined for your software organization.
    - - A software team should have a significant degree of flexibility in choosing the soft-ware process model that is best for the project and the software engineering tasks that populate the process model once it is chosen.
        
        work tasks for the communication activity:
        
        Develop list of clarification issues.
        
        Meet with stakeholders to address clarification issues.
        
        Jointly develop a statement of scope.
        
        Review the statement of scope with all concerned.
        
        Modify the statement of scope as required.
- - - - Information Objetives
        
        What customer-visible data objects are produced as output from the software? What data objects are required for input?
      - Function and Performance
        
        What function does the software perform to transform input data into output? Are any special performance characteristics to be addressed?
      - Context
        
        How does the software to be built fit into a larger system, product, or business context, and what constraints are imposed as a result of the context?