Please enable JavaScript.

Coggle requires JavaScript to display documents.

System Development - Coggle Diagram

- - - - Communication: Open communication among right players at the right time at the right level.
      - Feedback: frequent, meaningful feedback is recognized as best practice of software development.
      - Simplicity: Make a standard way of development among developers
      - Courage: Devs. should face rough/harsh choices of doing things right or throwing away bad code and starting over again.
    - - Planning
        
        Create a rough plan quickly then refine it as things become more clearer
        
        Reflects Agile Development as change is more important than detailed plans.
      - Testing
        
        Ensure each user story is tested correctly before it's programmed
        
        Intensifies Testing.
      - Pair Programming
        
        Two programmers work together on designing, coding and testing software
      - Simple Designs
        
        No code duplications, accomplish the desired result as few classes and methods as possible
        
        XP conforms to the principles of Agile Modeling
      - Owning the Code collectively
        
        Collective ownership allows anyone to modify any piece of code
        
        Everyone is responsible for the code he/she does.
      - Continuous Integration
        
        embodies the idea of Growing Software
        
        The code is integrated into system daily or more often after passing unit tests.
      - On-site Customer
        
        XP projects require users involvement as they make business decisions about functionality and scope
      - Refactoring
        
        Improve code to achieve simpler design without changing what it does
      - System Metaphor
        
        This term is easily understood by the development team.
        
        It help them understand the system.
      - Small releases
        
        Same as Continuous Integration, XP releases small and frequent upgraded solutions frequently to the users and keep them involved in the project for feedback.
      - Forty-Hour Week
        
        The project shouldn’t be a death march that burns out
        every member of the team
        
        the exact number of hours a developer works isn’t the issue.
      - Coding Standards
        
        XP devs follow coding and documentation standards.
    - - Project Activities
        
        Create User Story
        
        Create System Metaphor
        
        Create Acceptance Tests
        
        Plan Releases
      - Release Activities
        
        Plan Iterations
      - Iteration Activities
        
        Code
        
        Unit Test
        
        Integration
  - - - Product Backlog: High priority requirements are worked to be done at a time.
      - Product Owner:The client stakeholder for whom the system is built and responsible for project backlog and priorities.
      - Scrum Master: The project manager of the scrum project.
      - Scrum Team: Sets goals, organizes self and make decisions. The team is usually 5-9 people.
    - - Sprint
        
        Time-controlled mini project.
        
        Each sprint has its own backlog. The sprint backlog defines the scope
        
        The sprint should be delivered at most 30 day.
        
        The scope of that is sprint is frozen and No one change change it
      - Daily Scrum: 15-minutes daily meeting for all team members to report progress.
      - Sprint final half-day review: Review and identify changes needed for the following sprints.