Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Recently I had a couple of interesting experience. The scope of the project was signed off in the initiation stage, because of contractual constraints between vendor/consultants and the client organisation.
The project had a Project Manager and a Scrum Master, daily stand-ups, retrospectives, reviews,sprint planning BUT
1) The project Backlog was static, backlog items had separate tasks for BA, developer, tester and those roles were performed by specialised people.
2) There was only one release to production, after SIT and UAT.
Do you consider this project an Agile project? Saving Changes...
Rajesh PonnathotaSr IT Project Manager / Scrum Master / RPA Lead| Independent ConsultantSouth Windsor, Ct, United States
@Roman,
My bad, QA is Quality Analyst [Resource] and QC is Quality Control [Applies to Code]
It's not TRUE that the Quaity Contol happens after the entire project. You can move the developed code to QC Environment and get it tested after each Sprint in incremental way.
It's not necessary that the code should be moved to Production. We need to isolate the Code from Development Environment so QA Team can test it as stand-alone and report the defects. These defects should be fixed in the next Sprint / Iteration.
BTW, what your customer is saying is,
1. Do not have defects after releasing to production rather fix all the defects before.
2. After each Sprint completes, collect the feedback from the Customer so there are no surprises at the end [This is one primary reason, Projects moved from Lean approach to Agile approach]
Good news about your project is, Scope is finalized in the begining [You do not have to worry about Change Controls etc.,]. There is no such word called as Scope in Agile. Product Owner defines the Scope and Priority. Saving Changes...
Lenka PincotChief of Staff to the CEO| Project Management InstituteParis, France
Dan, that is very good question. I see agility more in the approach then in particular method. Agility is ability to respond, to learn and apply knowledge, to provide lean execution. We mostly consider agile project management in software development and sometimes we reduce it just to scrum. But if you want to say if a project was agile or not, I would look more on the way how it was done. For instance when you say the backlog was static, what do you mean exactly?
A) there was a list of things to do, defined in big detail upfront and just executed without any changes
B) there was high-level task list, each task was taken one by one, detailed and as we learned more and more, we adjusted the scope of the other tasks to better fit the project goal Saving Changes...
