In today s regulatory climate, companies cannot afford to have applications developed, or data housed, outside the boundaries of corporate oversight. Application failures lead to business process interruptions and lost revenue, and Lotus Notes applications are critical to the business. Their usefulness is reflected in the fact that many Fortune 500 companies have a significant investment in Lotus Notes and Notes applications. The trick is to tame Lotus Notes development, but not to break its spirit to provide Just Enough IT Governance to protect the company, without discouraging Lotus Notes development altogether. Strike the right balance to provide Just Enough Governance This book provides a set of policies and procedures designed to strike this balance, to provide Just Enough Governance for Lotus Notes. Firstly, it presents an IT governance philosophy for Lotus Notes that can protect the company without stifling developer initiative. Secondly, it gives IT staff and Notes developers a blueprint to implement IT governance processes and principles in the Lotus Notes environment. And finally, it takes a clear-sighted look at the future evolution of Notes and of IT governance. Good practices With the good practices presented here, you can create a governance process as agile as Notes itself, so that your business and Notes applications will prosper together for many years to come. This book is written by Craig Schumann who is Senior Vice President of R&D for Teamstudio. He has almost 12 years of experience with Lotus Notes and Domino(r), and has worked with Notes going back to R4. Before Teamstudio, he worked at IBM/Lotus. Key features * Lotus Notes and the trend towards IT governance * Just Enough Governance for Lotus Notes * Getting Started * Requirements * Design * Development * Test * Production * Convergence, IT governance and the future of Lotus Notes

Table of Contents

Introduction Chapter 1: Lotus Notes and the trend toward IT governance From the Wild West to business critical: the good, the bad, and the ugly Chapter 2: Just Enough Governance for Lotus Notes Gorging on governance vs. governance liteA" Chapter 3: Getting started Chapter 4: Requirements Aligning Notes development with corporate priorities Overview of the Requirements phase Steps in the Requirements phase Tools for request management and requirements definition Challenges of the requirements phase Moving from requirements to design Chapter 5: Design Design to deliver on requirements Overview of the Design phase Steps in the Design phase Tools for the design phase Challenges of the design phase Moving from design to implementation Chapter 6: Development Building in application quality Overview of the development phase Steps in the Development phase Tools for the Development phase Challenges of the development phase Moving from development to testing Chapter 7: Test The proof of the programming Overview of the Test phase Steps in the Test phase Tools for the test phase Challenges of the test phase Moving from test to production Chapter 8: Production A well-governed existence Overview of the Production phase The production environment for Lotus Notes Steps in the production phase Tools for the production phase Challenges of the production phase The proof is in production Chapter 9: Convergence, IT governance and the future of Lotus NotesWhither (not wither) Lotus Notes? Notes is alive and thriving Notes and service-oriented architecture Notes and Web 2.0 Changing roles Governing in good company Waking the lotus eaters Acronyms ITG Resources

About the Author

Craig Schumann is Senior Vice President of R&D for Teamstudio. He has almost 12 years of experience with Lotus Notes and Domino(R), and has worked with Notes going back to R4. Before Teamstudio, he worked at IBM/Lotus. At Teamstudio he is chiefly responsible for product strategy and R&D. He is an influential blogger in the Notes community, the author of many white papers, and articles on application development best practices for Lotus Notes, and is a highly respected writer in that space. In his years at Teamstudio, he has seen many Notes shops struggling then succeeding in getting their general Application Lifecycle Management procedures and practices right. These experiences have profoundly influenced his approach to Notes development, as he guides the evolution of the Teamstudio product line.Craig holds a B.S. in Computer Science from Wentworth Institute of Technology in Boston, and lives in Salem, MA with his wife and two boys. When he is not relaxing writing code, you can find him tearing up the unique, rocky single track found on the North Shore of Massachusetts, or taking a short, 40-mile lunchtime ride on his road bike.

Reviews

This bridges the gap between the Wild, Wild WestA" environment so often seen in Notes shops, and the approval- and documentation-heavy processes you see in other IT areas. Even better, it introduces the topic of governance in such a way that most Notes developers can relate to and accept. . I would highly recommend getting a copy of Just Enough Governance for Lotus Notes to make sure you're not exposing yourself and your company to unnecessary dangers. Thomas Duff, Lotus Notes Developer