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 116
... Project ROLES ACTIVITIES Rest and recreation Vacations & basic business Technical. Process Milestones Team Values Quality Teams Regression tests Object model Project plan Project manager Documenter Use cases Products Designer Roles ...
... Project ROLES ACTIVITIES Rest and recreation Vacations & basic business Technical. Process Milestones Team Values Quality Teams Regression tests Object model Project plan Project manager Documenter Use cases Products Designer Roles ...
Página 121
... Project sponsor Project manager Expert user Business expert Lead designer Ul expert Reuse point Designer / programmer Tester Writer Trainer Secretary Contractor Night watchman Janitor Envisioning Sales Requirements Test Proposal Setup ...
... Project sponsor Project manager Expert user Business expert Lead designer Ul expert Reuse point Designer / programmer Tester Writer Trainer Secretary Contractor Night watchman Janitor Envisioning Sales Requirements Test Proposal Setup ...
Página 158
... project manager can decide that the Smalltalk programmers can work " inefficiently , " meaning " doing more rework than they might otherwise , " in exchange for making their work more stable earlier . This means that the DBA , to whom ...
... project manager can decide that the Smalltalk programmers can work " inefficiently , " meaning " doing more rework than they might otherwise , " in exchange for making their work more stable earlier . This means that the DBA , to whom ...
Conteúdo
THE PROBLEM WITH PARSING EXPERIENCE | 3 |
THREE LEVELS OF LISTENING | 14 |
So What Do I Do Tomorrow? | 19 |
Direitos autorais | |
20 outras seções não mostradas
Outras edições - Ver todos
Termos e frases comuns
Adaptive Software Development Addison-Wesley agile methodology Agile Software Development apply artifacts 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 iteration Jim Highsmith Kent Beck language-games look meeting ment meth method methodol methodology design Object-Oriented odology 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 structure successful sweet spot tacit knowledge team lead team members techniques testers tests Theory Building View things Thoughtworks tion understanding unit tests user interface user stories whiteboard write