Edward KleinertClinical Assistant Professor| New York UniversityNew York, Ny, United States
Thanks Mike, Good overview of the change management process in effective project management. Comments or thoughts from others who are following this thread…? We invite all who are interested to share your thoughts. Saving Changes...
Mike FrenetteManager, IT PMO| Halifax Water (retired)Halifax, Nova Scotia, Canada
Yes, Edward ... I think I am done! :) Saving Changes...
Edward KleinertClinical Assistant Professor| New York UniversityNew York, Ny, United States
The balance between the Project Manager and the Business Analyst on a well-staffed and planned project makes for a crucial relationship between the team and the stakeholders. Understanding and executing their respective roles - the overall performance of the project (the PM) and the business needs of the organization (the BA) makes for a powerful combination. In what ways is this so…? Saving Changes...
Edward KleinertClinical Assistant Professor| New York UniversityNew York, Ny, United States
Your reaction...With the Business Analyst as the fulcrum...the project will always stay in balance... Saving Changes...
Edward KleinertClinical Assistant Professor| New York UniversityNew York, Ny, United States
Is the ‘Theory of Constraints’ (TOC) a relevant indicator to the challenges associated with the initiation of a project…? That is to say, engaging the ‘Business Owner’ and the ‘Discovery Team,’ in achieving a true understanding of the business need and its translation into project deliverables…?
Saving Changes...
Andy JordanPresident| Roffensian Consulting S.A.Cherry Grove, AB, Canada
I think that's fundamental Ed, the business need has to be the cornerstone to any project and if we aren't properly engaging the right people to ensure that the 'real' need is defined and understood then everything that follows is in jeopardy of failing to deliver the required results!
The fact that organizations continue to miss that understanding is extremely concerning. Saving Changes...
Edward KleinertClinical Assistant Professor| New York UniversityNew York, Ny, United States
Well stated Andy, There are core indicators that auger in favor of project success, one of the most compelling of which, is the alignment to an organizations mission, its vision, its strategy, and/or its business model. We don’t (should not) be conducting our work in our ‘own’ world…it needs to be work as a collective… Saving Changes...
Edward KleinertClinical Assistant Professor| New York UniversityNew York, Ny, United States
Let’s shift our focus just a little and get a take on the transferability of methodologies…specifically, ‘requirements traceability.’
Requirements traceability is a methodology associated with requirements management that is closely aligned with software development and systems implementation projects. It is about documenting the life of a requirement and providing traceability from its initiation through to the post go-live of the solution.
It enables users to track the need, into a specific deliverable, and to help ensure that the development of that deliverable (and its verification and validation) is in keeping with the original defined expectation of the customer; including any approved changes along the way.
To all comers…Do you consider this to be ‘unique’ to a systems project, or a fundamental methodology that all projects can benefit from when it comes to requirements management and delivering the intended results…?
Saving Changes...
Andy JordanPresident| Roffensian Consulting S.A.Cherry Grove, AB, Canada
I think traceability can apply to any type of project. Ultimately it is 'just' about making sure that everything required has been built and everything built is required. That's easier to define in systems projects, but the concept should apply to every project that we do. Saving Changes...
Mike FrenetteManager, IT PMO| Halifax Water (retired)Halifax, Nova Scotia, Canada
Totally agree, Andy. Any project with requirements can and should use traceability methods and tools.
Only projects with no requirements shouldn't worry about requirements traceability. [joke alert] Saving Changes...
