Informing myself about agile projects I get the impression this method is mainly used for software projects to get a first product fast and optimize afterwards.
I wonder if it makes sense to apply agile to an engineering development project, were the product is pretty clear as well as the way to develop it, but changes due to client wishes are common around once a quarter. More common and a cause for regular delay are changes in the priorization of the projects and therefore of the ressources.
Can the agile methods help to improve the setting / fulfilling of clear requirements (For sure in some way they can be used to change the way of working and therefore improving things)?
Did anybody use agile methods to reach a deeper commitment by the decision makers? Saving Changes...
Sort By:
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Actually, Gudrun, agile is about delivering value fast.
You have to prioritize your scope so you work on the most valuable pieces first. Then you focus on only a few pieces at a time so they get to be put to use as soon as possilble.
You can apply the same philosophy to just about any project in any industry. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First, agile is not software or IT related, agile is not a method, agile is not a process. So, you can apply agile from strategy formulation to strategy implementation. Second, if you will select a method to apply agile into your next initiative, some former agile software development methods are today agile solution delivery method (SCRUM and DSDM for example) I you have a lot of examples outside there to apply agile methods in non software (I can give you from my own experience but I have not written anything about that). My recommendation is: understand what agile really is and taking into account that it will impact the organization as a whole when you tried to apply it.
I have wrote a short article for PM Network about agile ("Perfectly Positioned": http://www.pmnetwork-digital.com/pmnetwork/april_2016?pg=73#pg73) and I have written a paper that was published by the PMI and IIBA as "best practices" that could help you in understand how this type of initiatives could be taken (https://www.projectmanagement.com/blog-pos...ight-solution). Hope that helps you.
...
2 replies by Abhijit Ganguly and Vincent Guerard
Jan 13, 2017 12:52 PM
Abhijit Ganguly
...
Thanks for sharing the link.
Jan 14, 2017 3:10 PM
Vincent Guerard
...
Sergio thanks for the links. You probably can publish a articles just with all the links you post on Agile here.
Saving Changes...
Abhijit GangulyDirector - Data Office| American ExpressScottsdale, Az, United States
Agile is best suited for environments where the requirements change frequently, the business wants to get value quickly and cannot wait for long periods. The key is to have business involvement for prioritizing and a cross functional team. Key to the success of any project is the commitment from the business. If you notice lack of attention or commitment for an extended period, you need to talk with the business. Saving Changes...
Abhijit GangulyDirector - Data Office| American ExpressScottsdale, Az, United States
Jan 13, 2017 12:27 PM
Replying to Sergio Luis Conte
...
First, agile is not software or IT related, agile is not a method, agile is not a process. So, you can apply agile from strategy formulation to strategy implementation. Second, if you will select a method to apply agile into your next initiative, some former agile software development methods are today agile solution delivery method (SCRUM and DSDM for example) I you have a lot of examples outside there to apply agile methods in non software (I can give you from my own experience but I have not written anything about that). My recommendation is: understand what agile really is and taking into account that it will impact the organization as a whole when you tried to apply it.
I have wrote a short article for PM Network about agile ("Perfectly Positioned": http://www.pmnetwork-digital.com/pmnetwork/april_2016?pg=73#pg73) and I have written a paper that was published by the PMI and IIBA as "best practices" that could help you in understand how this type of initiatives could be taken (https://www.projectmanagement.com/blog-pos...ight-solution). Hope that helps you.
Thanks for sharing the link.
...
1 reply by Sergio Luis Conte
Jan 13, 2017 1:41 PM
Sergio Luis Conte
...
You are welcome. Hope it helps at least to think about agile from other point of view.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Jan 13, 2017 12:52 PM
Replying to Abhijit Ganguly
...
Thanks for sharing the link.
You are welcome. Hope it helps at least to think about agile from other point of view. Saving Changes...
Thilo WackHead of Existing Product and Test Lab| optimedTholey-Hasborn, Germany
Gudrun,
agree with what my peers wrote. Agile is an adjective, not a method, framework or a process and its focus is on increasing the speed with which you provide value. So getting more agile will surely benefit all organizations and projects; however if fully adopting one of the agile frameworks (maybe after some customizing) is right for you is something that you'll have to find out for yourself. The question then is how to become more agile. There are some tools and frameworks (or parts of them, at least) that are totally independent of the project type / business environment. What I have started with is personal kanban and currently I am looking hard at how to implement daily stand-ups. I am also thinking about using sprints in executing traditionally planned projects, i.e. letting the team decide which activities of the backlog (=project plan) to deliver in 2-4 weeks and then have a retrospective. Another agile thing that seems very helpful in non-IT projects is how requirements are handled; I like the concept of user stories and the role of a product owner from the SCRUM framework.
If you search the content here you'll find a lot of articles and webinars on agile and I found especially those very helpful that talked about how to integrate agile practices into traditional or waterfall projects. Also I'd recommend Joseph Flahiff's book - Being Agile in a Waterfall World. You'll also find something from him on Youtube. I hope this will get you started and you'll let us know about your experiences... Saving Changes...
First, agile is not software or IT related, agile is not a method, agile is not a process. So, you can apply agile from strategy formulation to strategy implementation. Second, if you will select a method to apply agile into your next initiative, some former agile software development methods are today agile solution delivery method (SCRUM and DSDM for example) I you have a lot of examples outside there to apply agile methods in non software (I can give you from my own experience but I have not written anything about that). My recommendation is: understand what agile really is and taking into account that it will impact the organization as a whole when you tried to apply it.
I have wrote a short article for PM Network about agile ("Perfectly Positioned": http://www.pmnetwork-digital.com/pmnetwork/april_2016?pg=73#pg73) and I have written a paper that was published by the PMI and IIBA as "best practices" that could help you in understand how this type of initiatives could be taken (https://www.projectmanagement.com/blog-pos...ight-solution). Hope that helps you.
Sergio thanks for the links. You probably can publish a articles just with all the links you post on Agile here. Saving Changes...
Thanks everybody for your answers. It gives me some more to think of when and how to implement agile or agile tools.
Sergio, thank you for sharing the links
Thilo, this is exactly the question I'm trying to get a hold on, what is the right framework and what tools I can use, which will improve the project and be accepted (after a while) from the team members and other stakeholders.
Having seen quite some webinars and articles to this topic, it is still not clear enough for me, therefore the questions above. Saving Changes...
Thilo WackHead of Existing Product and Test Lab| optimedTholey-Hasborn, Germany
Gudrun,
I do understand that in a situation where you are unsure of the reaction of the team and the management up to the C-Suite you'd tend to be very careful and thoroughly plan your approach. We traditional project managers have been doing things that way for ages. But this is exactly what the agile movement wants to teach us: While there is value in planning, it is an activity with diminishing returns regarding the amount of work hours invested. The value of the work invested in planning all the details up-front is quickly getting very small as there will always be unplanned changes to the scope, the business environment, unforeseen issues etc. all leading to changes of the plan...Being agile will allow you to react to changes much faster and without you having invested a lot of work that will become obsolete with the change.
Maybe the better way for you would be the agile way: Just start small but in a way that immediately delivers value. Grab any agile practice that you like, that makes sense to you and persuade the team to give it a try. When they see and feel the value, i.e. something is working better, more efficient, with less hassle the change will stick and you can make the next step. Once you get results not only the team, but also your peers and ultimately the executives will notice and there will be very little resistance to do more of this and really become agile. Also on this journey you'll learn more about being agile and get a better understanding by your hands-on experience. This will help you when you need to make decisions about fully adopting a framework (if, when, why, what...). Saving Changes...
