Agile Software DevelopmentAddison-Wesley, 2002 - 278 páginas Written for developers and project managers, this book compares software development to a game. Team members play the game knowing that the ultimate goal is to win - always remembering what they have learned along the way, and always keeping in mind that they will never play the same way twice. Players must keep an open mind to different methodologies, and focus on the goal of developing quality software in a short cycle time. Based on a decade's work and research, and interviews with software project teams, this book presents sound advice for bringing difficult projects to successful conclusion with a minimum of stress. |
De dentro do livro
Resultados 1-3 de 19
Página 86
... iteration in order to meet the delivery schedule . Evant's XP team also used whiteboards and flipcharts as information radiators . Figure 3-9 shows the tasks for iteration " Mary Ann " ( each iteration was nick- named for someone on the ...
... iteration in order to meet the delivery schedule . Evant's XP team also used whiteboards and flipcharts as information radiators . Figure 3-9 shows the tasks for iteration " Mary Ann " ( each iteration was nick- named for someone on the ...
Página 165
... iterations . Each iteration results in run- ning , tested code that is of direct use to the customers . The compiled system is rolled out to its end users at the end of each release period , which may be every two to five iterations ...
... iterations . Each iteration results in run- ning , tested code that is of direct use to the customers . The compiled system is rolled out to its end users at the end of each release period , which may be every two to five iterations ...
Página 166
Alistair Cockburn. for the iteration onto simple index cards . The customer ( s ) and programmers nego- tiate what will get done in the next iteration in the following way : • The programmers estimate the time to complete each card ...
Alistair Cockburn. for the iteration onto simple index cards . The customer ( s ) and programmers nego- tiate what will get done in the next iteration in the following way : • The programmers estimate the time to complete each card ...
Conteúdo
THE PROBLEM WITH PARSING EXPERIENCE | 3 |
THREE LEVELS OF LISTENING | 14 |
A COOPERATIVE GAME OF INVENTION AND COMMUNICATION | 21 |
Direitos autorais | |
17 outras seções não mostradas
Outras edições - Ver todos
Termos e frases comuns
activity Adaptive Software Development Agile Software Development Alistair Cockburn apply behavior Cockburn cooperative game cost create Crystal Clear Crystal Orange culture deliver described diagrams discussion documentation effective example experience Extreme Programming feedback Figure game of invention goal grammers gramming Highsmith ideas increment information radiators interview invention and communication iteration Jim Highsmith Kent Beck language-games look ment meth methodol methodology design notice Object-Oriented odology osmotic communication pair programming person Personal Software Process practice principle problem project manager project team question reflection workshop regression tests requirements role situation skills Smalltalk Smalltalk programmers software development someone sponsors story strategy success sweet spot tacit knowledge team members techniques testers Theory Building View things Thoughtworks tion understanding user interface user stories whiteboard write