The project manager's toolkit : practical checklists for systems development /
David M. Shailer.
- xiii, 244 pages ; 25 cm.
- Computer weekly professional series .
- Computer weekly professional series .
Computer Weekly Professional Series -- Preface -- Acknowledgements -- Project Inception Checklists -- Getting the project kick-off meeting right -- Five key areas to understand when starting a project -- Dealing with hidden agendas - where to start -- How to do a simple risk assessment -- Twelve project procedures to have in place before you start -- Determining the big three - targets, timescales and budgets -- Nine tell-tale signs of a project nightmare -- How long is a piece of software? -- How should I staff a project? -- Project trade-offs - how to tease them out upfront -- What sort of project lifecycle should I adopt? -- Make or buy - deciding the package or bespoke development question -- Some do's and don'ts of package selection -- Project Control Checklists -- Five things to be checked throughout the project lifecycle -- Spotting a project runaway before it happens -- Three key communication issues to get right -- How to cut a project down to size -- How to avoid wasting time on things that don't matter -- Different ways of generating solutions for a problem -- Setting up a document-naming standard -- How do I manage a piece of software? -- Business Analysis Checklists -- Nine key questions for high-level business understanding -- How do we analyse our relationship with our customers? -- Fourteen common business problems - spotting which ones are yours -- Where business analysis usually goes wrong -- What are the steps to analyse a business process? -- What are the techniques for describing a business process? -- Four problems with business process diagrams and how to fix them -- Quality checks for a business process model -- How to identify what's bad in a business process -- Clarifying the business goal -- Ways of picking a business-modelling technique -- Four key areas to a process -- Lines of questioning for a business process -- How to choose between alternative solutions for changing a business process -- Checking the redesigned process -- Business process redesign - power tool #1 - partnering -- Business process redesign - power tool #2 - IT -- Business Requirements Checklists -- Prototyping for requirements the big issues -- Six steps in a requirements-gathering prototype -- Easy things to miss in gathering requirements -- What documents should I produce? -- How good is my Business Requirements Specification? -- Systems Analysis Checklists -- What should be in a methodology? -- How do you make a methodology? -- Moving from current physical to current logical -- System boundary analysis for requirements -- Functional priority analysis - applying the 80:20 rule -- Shortcuts to move from business process analysis to systems analysis -- What's in a system specification? -- General quality checks for a system specification -- Checking a logical design -- Six steps to first-cut data requirements -- How to do data modelling -- Object orientation development steps for a data-centric approach -- System Build Checklists -- What logical data models get wrong (and have to be put right) -- Database physicalization - five areas of useful tips and tricks -- Seventeen quality checks for a physical data model -- What modules to add into every application build -- Individual module quality - key questions to ask -- Transactions and how to design them -- What to include in common error detection and handling -- How to distribute modules to servers -- Finding the big four performance bottlenecks -- Why projects don't achieve software reuse -- How to find the causes of extremely elusive errors -- four standards to apply to the user interface -- QA and Testing Checklists -- Establishing the need for testing and QA -- Setting the scope for testing - avoiding the bottomless pit -- Ensuring a mix of testing types is present in a project -- What to test at two key milestones of a project -- Setting up the test team - personnel and policies -- What test documentation should I maintain for application testing? -- Where to get test data from for application testing -- General tests to apply to a screen -- How to generate test data for screen fields (domains) -- How to prioritize errors and grade the acceptance of functions -- Power testing 1 - checking the underlying database -- Power testing 2 - thrashing and crashing the system -- Power testing 3 - checking the business controls -- System Implementation Checklists -- Change-auditing and change-capacity assessment - how to see the big picture -- Things to plan for in an implementation -- Adopting the NASA go/no-go list -- How to build a training course -- Seven pillars of a service level agreement -- What to look at when capacity planning -- How to do a data conversion -- Nine important documents to hand over from development to the support team -- Assessing the long-term viability of a system -- After implementation - living with the system -- Questions to ask at the post-implementation review. 1. 1.1. 1.2. 1.3. 1.4. 1.5. 1.6. 1.7. 1.8. 1.9. 1.10. 1.11. 1.12. 1.13. 2. 2.1. 2.2. 2.3. 2.4. 2.5. 2.6. 2.7. 2.8. 3. 3.1. 3.2. 3.3. 3.4. 3.5. 3.6. 3.7. 3.8. 3.9. 3.10. 3.11. 3.12. 3.13. 3.14. 3.15. 3.16. 3.17. 4. 4.1. 4.2. 4.3. 4.4. 4.5. 5. 5.1. 5.2. 5.3. 5.4. 5.5. 5.6. 5.7. 5.8. 5.9. 5.10. 5.11. 5.12. 6. 6.1. 6.2. 6.3. 6.4. 6.5. 6.6. 6.7. 6.8. 6.9. 6.10. 6.11. 6.12. 7. 7.1. 7.2. 7.3. 7.4. 7.5. 7.6. 7.7. 7.8. 7.9. 7.10. 7.11. 7.12. 7.13. 8. 8.1. 8.2. 8.3. 8.4. 8.5. 8.6. 8.7. 8.8. 8.9. 8.10. 8.11.