I'd Like One IT Project To Go -- and Supersize It (Part 2)
Last week’s article emphasized the importance of establishing a concrete project organization and a strong project foundation when embarking on a DW project. Now it's time to move on to the project's execution. Specifically, we're going to give you ideas for creating some basic tools to assist with the day-to-day workings of the project. These tools, if used consistently and correctly, can help you avoid unforeseen difficulties keep the team and team members accountable and on track and provide a method to capture, document and resolve project issues or problems.
Build time into the plan for team reviews. Invite DBAs and ETL (Extract, Transform and Load) leads to logical and dimensional design reviews early in the design process. While this may seem like a distraction for the logical designers, it will pay off during database design and ETL implementation. The trick will be to minimize or eliminate the ongoing arguments about design issues, performance issues and even naming conventions. Build time into the plan for at least one iteration of changes followed by a subsequent review of those changes. Decide in advance who has ultimate authority and final word on design changes. Set a deadline for completion of design changes.
Build time into the plan for peer reviews (internal team reviews): These reviews are for technical people and are
Please log in or sign up below to read the rest of the article.
|
"Life is what happens to us while we're making other plans." - John Lennon |




