000 | 03227nam a22003615i 4500 | ||
---|---|---|---|
001 | 284579 | ||
003 | MX-SnUAN | ||
005 | 20160429154331.0 | ||
007 | cr nn 008mamaa | ||
008 | 150903s2005 xxu| o |||| 0|eng d | ||
020 |
_a9781430200086 _99781430200086 |
||
024 | 7 |
_a10.1007/9781430200086 _2doi |
|
035 | _avtls000336548 | ||
039 | 9 |
_a201509030821 _bVLOAD _c201404300318 _dVLOAD _y201402041352 _zstaff |
|
040 |
_aMX-SnUAN _bspa _cMX-SnUAN _erda |
||
050 | 4 | _aQA76.758 | |
100 | 1 |
_aGunderloy, Mike. _eautor _9312432 |
|
245 | 1 | 0 |
_aPainless Project Management with FogBugz / _cby Mike Gunderloy. |
264 | 1 |
_aBerkeley, CA : _bApress, _c2005. |
|
300 |
_a208 páginas _brecurso en línea. |
||
336 |
_atexto _btxt _2rdacontent |
||
337 |
_acomputadora _bc _2rdamedia |
||
338 |
_arecurso en línea _bcr _2rdacarrier |
||
347 |
_aarchivo de texto _bPDF _2rda |
||
500 | _aSpringer eBooks | ||
505 | 0 | _aMaking Project Management Work -- The FogBugz Philosophy -- Lifecycle of a FogBugz Case -- Managing Cases -- The Three Types of Cases -- Where Do Cases Come From?- Entered via Web Interface (local/customer) -- Entered via e-mail -- BugzScout -- Screenshots and attached files -- Filtering cases -- Being a Good FogBugz Citizen -- How devs/qa/mgt should work with FB -- Making FogBugz work for you -- Setting up Users and Groups -- Setting up Projects etc -- Setting up Permissions -- All the other lists you can change -- Getting the Big Picture -- Tracking estimates -- Using Due Dates -- Resolving cases -- Creating Release Notes -- Reporting/Extending -- Working with E-mail, RSS, and Discussion Groups -- E-mail -- Subscribing -- Customer e-mail -- RSS -- Discussion Groups -- Working with Source Code Control -- Setting up SCC -- Getting from Cases to Code and vice versa -- Appendix A: Setting up FogBugz -- Installing on Windows -- Installing on Unix -- Installing on MacOSX -- Customizing FogBugz -- Overall -- User options -- Appendix: BugzScout sample code. | |
520 | _aMany programs purport to help a development team manage a project but most of them aren’t very good. Enter FogBugz. This dynamic tool is based on keeping track of a database of cases. At any given time, cases are assigned to one person, who must resolve or forward them to someone else. With FogBugz, cases can be prioritized, documented, sorted, discussed, edited, assigned, estimated, searched, and tracked. And because FogBugz is web-based, everyone on a development team has access to the whole picture, at any given moment. That picture may include everything from customer feature requests, to high-level design discussions, to tiny bug fix details. This book (written under the guidance of the entire FogBugz team) completely describes the ins and outs of the latest version of FogBugz. | ||
590 | _aPara consulta fuera de la UANL se requiere clave de acceso remoto. | ||
710 | 2 |
_aSpringerLink (Servicio en línea) _9299170 |
|
776 | 0 | 8 |
_iEdición impresa: _z9781590594865 |
856 | 4 | 0 |
_uhttp://remoto.dgb.uanl.mx/login?url=http://dx.doi.org/10.1007/978-1-4302-0008-6 _zConectar a Springer E-Books (Para consulta externa se requiere previa autentificación en Biblioteca Digital UANL) |
942 | _c14 | ||
999 |
_c284579 _d284579 |