GoConqr has a new look! Let us know what you think.

Sign up free

Flashcards

Extreme Programming

DULCE LIZBETH FUENTES VILLA English 12 cards

Extreme Programming

Cards in this deck (12)

  1. 1Extreme ProgrammingIt is a framework design to improve the quality of the software and its ability to properly adapt to the changing.XP provide iterative and frequent small releases throughout the project.It's important the contact between the costumer and the team members in order to review the project.
  2. 2EXtreme valuesSimplicity
    We will do what is needed, but no more    EXtreme valuesEXtreme values
  3. 3Communication Everyone is part of the teaand we communicate face to face daily no more of fifteen minutes.Feedback
    The process to take information and improve the project(New realeses)    Communication Everyone is part of the teaand we communicate face to face daily no more of fifteen minutes.Communication Everyone is part of the teaand we communicate face to face daily no more of fifteen minutes.
  4. 4Respect It's accept the comments from each member of the team.The new ideas are accepted.(Positive thinking)Courage
    it's take the truth about progress and estimates.We don´t fear anything because no one ever works alone.    Respect It's accept the comments from each member of the team.The new ideas are accepted.(Positive thinking)Respect It's accept the comments from each member of the team.The new ideas are accepted.(Positive thinking)
  5. 5Extreme Rules(phases)1.-Planning(user stories)
    User stories are written
    Release planning creates the release schedule
    The project is divided into iterations
    Iteration planning starts each iteration    Extreme Rules(phases)
  6. 62.-Managing Give the team a dedicated open work space Set a sustanaible pace A stand up meeting starts each day The project Velocity is measured Move people around Fix Extreme programming when it breaks.3.-Designing
    Simplicity
    Choose a system metaphor
    Use CR cards for design sessions
    Create spike solutions to reduce risk
    No functionality is added early
    Refactor whenever and wherever possible.
  7. 74.-Coding The customer is always avilable Code mustbe written to agreed standards Code the unit test first All production code is pair programmed Only one pair integrates code at a time Integrate often Set up a dedicated integration computer Use collective ownership5.-Testing
    All code must have unit tests
    All code must pass all unit tests before it can be released
    When a bug id found tests are created
    Acceptance tests are run often and the score is published
  8. 8Extreme Practices The best practices of software development.Twelve Extreme programming Best Practices detail the way to follow at the time to programming.Pair programming
    It means that two people work in tandem on the same system when is developing.
  9. 9Planning game It takes the form of a meeting at a frequent and wel-defined interval(every one or two weeks)Exploration phase
    Story cards are used to detail the mos valuable requirements from customers.
  10. 10Steering phase It's equals to gandProjectExploration phase
    All project requirements are written down.
  11. 11Steering phase Developments taskes place and,upon completion the resulting iteration is compared to the outline story cards.Test-driven development
    The testing is used with each improve of the project
  12. 12Whole team SDLC and practices.Extreme programming promotes the inclusion of customers and clients throughout the entire process.(Using the feedback)Continuos process-integration
    Another common practice in modern development,theidea behind continuos integration.

Information

Description
Flashcards on Extreme Programming, created by DULCE LIZBETH FUENTES VILLA on 31/01/2019.
Views
11
Rating

Feedback

What is it about?

What do you think of the new look?

How do you like it?