Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Dec 13, 2017 3:32 PM
Replying to Ezara Penning
...
Sergio, thank you for the "eureka" moment. Much of my learning has been focused on the details that I have not been able to see the overarching problem and how to identify and then remedy it. I have definitely learned a lot today!
You are welcome. My recommendation is taking a look to USA DoD NSF/Agility Forum deliverables or searching into the internet for Rick Dove´s work "Response Ability" because it contains most of the results due to Rick was the program manager on charge of the forum. Saving Changes...
Jose Luis Gonzalez RugelPresidente Grupo Gonzalez - Program Manager - Docente- Consultor - ATP Trainner| DipromacomGuayaquil, Guayas, Ecuador
A friend says that Agile is a way of life and is based on 12 principles that are:
-Customer satisfaction. It is the basis of everything. It is achieved through the delivery of valuable products that meet a need.
- Welcome the new requirements. Changing on the fly is not taking a step back. Any suggestion or solution is welcome if it is about improving the product.
- Delivery for weeks The division of labor into productive phases is the basis of the methodology. Where possible, run one every week.
- It is possible to measure progress. The evolution of processes is not a subjective element. It can be measured with concrete indicators.
- Sustainable development. The way of executing the projects must guarantee its continuity in itself. It is not a matter of doing.
- Close work. The leaders of the projects must work in the same field where the tasks take place and not from the offices.
- Face to face conversation The responsible manager must communicate effectively their messages, better if done in person. Regular meetings are recommended both with the client and with his collaborators.
- Motivation and trust The processes will only be successful if those who carry them out are motivated people who interact in climates of trust and solidarity.
- Technical excellence and good design. The forms should never be lost, nor should the quality of the work. Everything is a whole.
- Simplicity The tasks must be as simple as possible. If any can not be executed in those terms, it must be divided into iterations until its level of complexity is reduced.
- Self-management of equipment. Although there must be a figure that monitors the work teams, they must be able to organize themselves. The excess of hierarchies creates dependency among collaborators.
- Adaptation changing circumstances. Projects do not usually end the same way they started. It is essential that those who execute them can adapt to the different circumstances that may arise. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Dec 13, 2017 9:26 AM
Replying to Sergio Luis Conte
...
JAJAJAJJA, Thank you very much my friends. Here I am. First of all, I always comment about Agile because I firmly believe that the general confusion outside there jeopardizes the work for all of us and mainly the intentions of people that are trying to find a job. All I will write as follows can be checked and my only objective is that: search for the basement and the real information. Here I comes. By definition, the definition created in 1990 inside the USA DoD NSF/Agility Forum and then taking by creators of methods for software development based on Agile (I worked with some of them like Arie Van Bennekum) Agile is "a way of behave and thinking with focus on client and quality". When you use behave Agile then you gain into agility which is "the ability to respond to changes and to create changes". That is the reason because Agile is not the same of Lean, while Agile was born trying as an innovation on Lean.
I personally was waiting for you Sergio haha :D
...
1 reply by Sergio Luis Conte
Dec 13, 2017 9:54 PM
Sergio Luis Conte
...
JAJAJA! Thank you very much. Believe me, I spend time here because I learn a lot for your comments and other comments and it helps me a lot to improve myself.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Dec 13, 2017 4:46 PM
Replying to Rami Kaibni
...
I personally was waiting for you Sergio haha :D
JAJAJA! Thank you very much. Believe me, I spend time here because I learn a lot for your comments and other comments and it helps me a lot to improve myself. Saving Changes...
Robert Edison de LeonProject Manager| Globe TelecomTaguig, Metro Manila, Philippines
Thanks Friends for I am learning a lot from you. Is it correct or not to assume that for as long we deliver the scope of our projects on time, within budget, with quality and with our stakeholders happy, we are on the right track regardless whether we are using Agile or not? :)
...
1 reply by Sergio Luis Conte
Dec 14, 2017 5:52 AM
Sergio Luis Conte
...
That´s the point @Robert. You are right. What you stated is totally independent to the practice you are using. For example, you can use Agile practice with waterfall life cycle, Key is to understand that anything you use will impact the organization as a whole (systemic theory applied to organizations). I saw you are working in Telecom. I helped one of the top three organizations to use Agile (we use an Agile based method in this case) into an initiative where the main objective was to install 4G technology to get a dominant position in that field before its competitors. It was a software based project? Not at all. The key component was to install antennas. Why to use Agile? The driver was to create a change into the environment that made others to follow it. How the organization decide it? Taking into account the type of product to create, the environmental conditions, the organizational architecture.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Dec 13, 2017 10:47 PM
Replying to Robert Edison de Leon
...
Thanks Friends for I am learning a lot from you. Is it correct or not to assume that for as long we deliver the scope of our projects on time, within budget, with quality and with our stakeholders happy, we are on the right track regardless whether we are using Agile or not? :)
That´s the point @Robert. You are right. What you stated is totally independent to the practice you are using. For example, you can use Agile practice with waterfall life cycle, Key is to understand that anything you use will impact the organization as a whole (systemic theory applied to organizations). I saw you are working in Telecom. I helped one of the top three organizations to use Agile (we use an Agile based method in this case) into an initiative where the main objective was to install 4G technology to get a dominant position in that field before its competitors. It was a software based project? Not at all. The key component was to install antennas. Why to use Agile? The driver was to create a change into the environment that made others to follow it. How the organization decide it? Taking into account the type of product to create, the environmental conditions, the organizational architecture.
Agile is a project management methodology that uses short development cycles called "sprints" to focus on continuous improvement when developing a product or service.
The Project Management Institute (PMI) states "Agile approaches to project management aim for early, measurable ROI through defined, iterative delivery of product increments. They feature continuous involvement of the customer throughout the product development cycle. Although agile has its roots in software and IT, agile adoption is growing and expanding in a wide range of industries." https://www.pmi.org/learning/featured-topics/agile
I would like to add "retrospective meetings" which takes place after completing each Sprint. This allows the lessons learned implemented in the upcoming Sprints. This allows better quality on forthcoming sprints. This is one good advantage in Agile. Saving Changes...
Jim BrandenSenior Project Manager| Retired from UNC Charlotte - IT Services - PPMOCharlotte, Nc, United States
Amir,
Your question used the word “agile” rather than the word “Agile”. To get to the heart of “Agile” go to http://agilemanifesto.org/
There are many websites and organizations, using and abusing “Agile” and “agile”! As a PM-Instructor, one of my mantras paraphrases my understanding of PMI’s fundamental thinking: “Use the appropriate tools on the appropriate projects, appropriately!”
I managed projects for 25 years building WBSs before I learned they have a name. Likewise, many of those projects were software development and my team used the appropriate tools, years before ‘17 guys’ decided to write the “Agile Manifesto”.
Wish I had named the tools and started selling credentials.
Anyone want to join me in writing the “Nimble PM Manifesto”? We could use Agile tools and techniques!
Jim Saving Changes...
Robert Edison de LeonProject Manager| Globe TelecomTaguig, Metro Manila, Philippines
Dec 14, 2017 5:52 AM
Replying to Sergio Luis Conte
...
That´s the point @Robert. You are right. What you stated is totally independent to the practice you are using. For example, you can use Agile practice with waterfall life cycle, Key is to understand that anything you use will impact the organization as a whole (systemic theory applied to organizations). I saw you are working in Telecom. I helped one of the top three organizations to use Agile (we use an Agile based method in this case) into an initiative where the main objective was to install 4G technology to get a dominant position in that field before its competitors. It was a software based project? Not at all. The key component was to install antennas. Why to use Agile? The driver was to create a change into the environment that made others to follow it. How the organization decide it? Taking into account the type of product to create, the environmental conditions, the organizational architecture.