Home > Articles > Networking > Storage

📄 Contents

  1. 1.1 Building a Site from Scratch
  2. 1.2 Growing a Small Site
  3. 1.3 Going Global
  4. 1.4 Replacing Services
  5. 1.5 Moving a Data Center
  6. 1.6 Moving to/Opening a New Building
  7. 1.7 Handling a High Rate of Office Moves
  8. 1.8 Assessing a Site (Due Diligence)
  9. 1.9 Dealing with Mergers and Acquisitions
  10. 1.10 Coping with Frequent Machine Crashes
  11. 1.11 Surviving a Major Outage or Work Stoppage
  12. 1.12 What Tools Should Every SA Team Member Have?
  13. 1.13 Ensuring the Return of Tools
  14. 1.14 Why Document Systems and Procedures?
  15. 1.15 Why Document Policies?
  16. 1.16 Identifying the Fundamental Problems in the Environment
  17. 1.17 Getting More Money for Projects
  18. 1.18 Getting Projects Done
  19. 1.19 Keeping Customers Happy
  20. 1.20 Keeping Management Happy
  21. 1.21 Keeping SAs Happy
  22. 1.22 Keeping Systems from Being Too Slow
  23. 1.23 Coping with a Big Influx of Computers
  24. 1.24 Coping with a Big Influx of New Users
  25. 1.25 Coping with a Big Influx of New SAs
  26. 1.26 Handling a High SA Team Attrition Rate
  27. 1.27 Handling a High User-Base Attrition Rate
  28. 1.28 Being New to a Group
  29. 1.29 Being the New Manager of a Group
  30. 1.30 Looking for a New Job
  31. 1.31 Hiring Many New SAs Quickly
  32. 1.32 Increasing Total System Reliability
  33. 1.33 Decreasing Costs
  34. 1.34 Adding Features
  35. 1.35 Stopping the Hurt When Doing This
  36. 1.36 Building Customer Confidence
  37. 1.37 Building the Teams Self-Confidence
  38. 1.38 Improving the Teams Follow-Through
  39. 1.39 Handling an Unethical or Worrisome Request
  40. 1.40 My Dishwasher Leaves Spots on My Glasses
  41. 1.41 Protecting Your Job
  42. 1.42 Getting More Training
  43. 1.43 Setting Your Priorities
  44. 1.44 Getting All the Work Done
  45. 1.45 Avoiding Stress
  46. 1.46 What Should SAs Expect from Their Managers?
  47. 1.47 What Should SA Managers Expect from Their SAs?
  48. 1.48 What Should SA Managers Provide to Their Boss?
  • Print
  • + Share This
This chapter is from the book

1.34 Adding Features

  • Interview customers to understand their needs and to prioritize features.
  • Know the requirements—Chapter 5.
  • Make sure that you maintain at least existing service and availability levels.
  • If altering an existing service, have a back-out plan.
  • Look into building an entirely new system and cutting over rather than altering the running one.
  • If it’s a really big infrastructure change, consider a maintenance window—Chapter 20.
  • Decentralize so that local features can be catered to.
  • Test! Test! Test!
  • Document! Document! Document!
  • + Share This
  • 🔖 Save To Your Account

Related Resources

There are currently no related titles. Please check back later.