tag:blogger.com,1999:blog-57075225838994635612011-04-21T19:01:53.774-07:00Project Management Starhttp://www.blogger.com/profile/15628705723869288822noreply@blogger.comBlogger11100tag:blogger.com,1999:blog-5707522583899463561.post-906657337414002072008-05-23T06:28:00.000-07:002008-05-23T09:08:06.802-07:00I recently ran across a new way to minimize the disruption of my projects that are currently underway from "emergency requests/projects" that come in out of left field. I have found it to be quite effective.<br /><br /><em><strong>GRD Process</strong> - Project Management process for handling out of cycle high priority projects with minimal disruption to in-flight project. GRD team is made up of only team members who are absolutely core to the completion of the emergency project (typically Development, QA, Product). Project Manager exists to communicate status to non core team members (to avoid interruption), to extract information needed from non-core team to resolve any open issues and to aide in the removal of any overall dependencies.</em><br /><br />I have found this to be most effective when managing Projects related to Website Feature Development. Typically these projects already have short durations, and the impact that emergency projects/requests have can be tremendous. I have found that putting the GRD process into practice has decreased the disruption from "emergency requests/projects" and kept the team moving along on our current sprint cycle with minimal overall impact/distraction. I simply love it!!!<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5707522583899463561-90665733741400207?l=project-management-excellence.blogspot.com' alt='' /></div>Project Management Starhttp://www.blogger.com/profile/15628705723869288822noreply@blogger.com0