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 62
Página 32
... tion more . Suddenly the people who elected to join a profession that did not require much interpersonal communica- tion are being asked to become good at it . Only the universities can reverse the general characteristics , by creating ...
... tion more . Suddenly the people who elected to join a profession that did not require much interpersonal communica- tion are being asked to become good at it . Only the universities can reverse the general characteristics , by creating ...
Página 97
... tion in a conversation doesn't , a stickiness you sometimes want . The person who went to Russia with the use cases wanted to make sure that he did not forget what he was supposed to cover in his conversations . He wanted to make sure ...
... tion in a conversation doesn't , a stickiness you sometimes want . The person who went to Russia with the use cases wanted to make sure that he did not forget what he was supposed to cover in his conversations . He wanted to make sure ...
Página 175
... tion is insufficient . LOOKING FOR DOCUMENTATION A programmer told of his company rewrit- ing their current core product because there is no documentation , no one is left who knows how the system was built , and they are unable to make ...
... tion is insufficient . LOOKING FOR DOCUMENTATION A programmer told of his company rewrit- ing their current core product because there is no documentation , no one is left who knows how the system was built , and they are unable to make ...
Conteúdo
A Cooperative Game of Invention and Communication | 21 |
SOFTWARE AND POETRY | 23 |
SOFTWARE AND GAMES | 25 |
Direitos autorais | |
40 outras seções não mostradas
Outras edições - Ver todos
Termos e frases comuns
activity agile methodologies Agile Software Development Alistair Cockburn 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 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 pair programming participants person Personal Software Process Peter Naur practice principle problem program text project manager project team question Recovery action reflection workshop regression tests requirements role rules situation skills Smalltalk someone sponsors story strategy successful sweet spot tacit knowledge team members techniques testers Theory Building View things Thoughtworks tion understanding user interface user stories whiteboard write