Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
Have other members of PMI discovered that in project teams , you come across team members that tend to be stuck up on terminology , especially if there are different approaches to completing the project?
For example, if they are used to "Sprints", either because they have learnt it on a course or used it on projects as opposed to "Iterations", they make it a point to tell you or give the impression that they are not willing to adapt.
They wan't to see "Done" on the Kanban board instead of "Complete".
They cannot fathom "In progress" being divided into Development and Testing or cannot see Development and Testing to be combined into "in Progress"
I would have thought you can tailor the use of these terms on different types of projects where you expect "Rapid Delivery" and I certainly don't have an issue adapting myself.
And sometimes the argument is "The software tool (e.g. JIRA) defines it this way, so it HAS to be this way..."
Why wouldn't team members simply concentrate on the end product and be willing to tailor the "means" to getting there? Saving Changes...
