Please login or join to subscribe to this thread
Yes, we are currently delivering IT infrastructure projects in Agile. But they are purely infrastructure projects, not business projects with infrastructure stream/component. What exactly is your area of interest related to this?
Yes, but it depends on the scope of the project. If you are doing an infrastructure project which has to be delivered in a single "big bang" release, then you can certainly leverage agile values & principles and certain practices, but you won't be realizing business value early and regularly.
On the other hand, if you can phase in the deliverables, then sure!
Sprint duration may need to be adjusted from the common default of 2 weeks as certain activities may require longer. In some cases, a lean Kanban approach might be a better fit than a sprint-based one.
Good question. I’d suspect there would be varying factors that would help determine the best approach for a given project/effort.
I took over for a PM once who was going to be out of work for over a month. The only thing from Scrum they had were the daily Scrums. No Sprints, no retros, no planning meetings.
When she got back I asked about it because the project seemed perfect for an iterative approach and could have certainly benefited from retrospectives and structured planning. She apparently intended to bring Scrum in and use it but got no business support. No one wanted to try and look at it iteratively, they just wanted the work done and not think about it. So she had no business support and they just dumped new requirements on her all the time. In her words, it was a mess. A mess that probably could have been helped by a more formal and rigid Agile approach.
Unlike in software, in hardware iterative means pure waste from the delivery point of view. Simple things like moving a blade in the chassis is waste, it doesn't add any value to the end user.
We are using Scrum and we are using Agile practices with other life cycles.
It is not just IT infrastructure probably all software implementation projects deliver in a single "big bang" release and that's why agile is failing in most big projects.
When I am saying agile is failing I am not saying that the projects fail I am saying that those that are delivering pretend they are doing agile but in reality they are not. Many projects no matter the domain simply don't allow you to build in small iterations.
Usually what's left from agile is the managements of the user stories in a software. Sprints usually are kept too but they make no sense as they don't deliver anything to the customer.
Please login or join to reply