I am new in this area of project management and recently i got involved in my first project, that is why i am very interested of the Agile Management Concepts. I think i will adopt this softwear for a steady, pragmatic approach to avoid the pitfalls, as well as i will adapt Agile for my business and industry. Saving Changes...
Vishakha SharmaPMP, PSM, Sr Project Manager, Agile and Scrum, Delivery Manager| Artha Learning, Swiftwin, Tech Mahindra Ltd, Upside Learning Solutions Pvt LtdPune, Maharashtra, India
Agile helps to deliver faster, reach out to market quickly, accommodate feedback as the project progresses. What it doesn’t support is extensive documentation and upfront planning. Saving Changes...
Agile is not a methodology but rather a set of values, principles supported by practices and tools.
So rather than commenting on agile, I will provide pros and cons of an adaptive lifecycle.
Pros:
- better for handling higher degrees of uncertainty and/or complexity
- potential for earlier ROI if scope can be delivered and used by customers incrementally
- potential for reduced rework or other forms of waste such as unused features
Cons:
- situations where the above factors are not applicable
Kiron Saving Changes...
Jesus MartheynProject Manager SR Lvl 2| GlobantMedellin, Antioquia, Colombia
Hi Valentin,
I agree with Kiron, Agile is not a methodology but I'll share my points from Scrum.
Pros:
- The customer receives what he needs and what he expects
- The return of investment is faster than traditional PM.
- You can deploy your product since the first sprint rather than wait until the end of the project
Cons:
- There are some lacks related to schedule and cost management, and that's why the traditional PM is required to support the project but at a high level.
- Documentation could be a problem if the team doesn't assume so as a task to work on. Saving Changes...
Pros of Agile:
flexibility of task/phase scheduling and prioritization
greater transparency to the product owner, sponsor, and business in general
early and often deliverables/prototypes (so less chance of misinterpretation of reqts)
Cons of Agile:
strong teamwork required
requires involvement of product owner/sponsor
possibly less efficient when rework or retrofitting is needed due to sprint timelines
responsibility for vendor/contract management can be convoluted Saving Changes...
Cons:
Customer availability is must
Customer should be clear about final outcome
Hard to calculate total effort and cost to deliver project Saving Changes...
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
Pros:
Commitment
Teamwork
Co-location
Alignment
Business Involvement Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The worst thing you can do is talking about strong or weak without context. Mainly when you think that Agile is a method or methodology. Agile is not a method, Agile is not a process or life cycle, Agile did not start with the Manifesto, Agile is not software related (in fact, the Manifesto use the word software into its name for a reason). You can apply Agile into any context. Basement about Agile is having an enterprise architecture with able a way of thinking and behave with focus on client, value and quality. The other thing mostly forgotten is the product/service/result you will create. Solution is equal to "the thing" to be created plus "the way" to create it. Both must be taken into account. Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
If you want to run a Project as Agile, unless you get continuous engagement and involvement with your key stakeholders and your project sponsor throughout the project, it will fall down on a big heap. They have to be committed to be available when you need them and you will need your product owner every step of the way.
Also , management and stakeholder buy in is a must . You need to clearly explain the agile manifesto and make sure that they understand that you WILL be producing documentation , but your main focus will be on Interactions , which will eventually make the documentation tasks easier.
You need to explain that your project will produce incremental value , something tangible that you can see after every iteration/sprint Saving Changes...
Lenka PincotChief of Staff to the CEO| Project Management InstituteParis, France
When deciding which approach to choose, it’s always very important to see the rest of the organization, working culture and other processes in place. There are several methods for agile software delivery, but in broader sense agility is about being able to learn and adapt. It works great with smaller teams and similar minded stakeholders, but you may start facing challenges when the rest of the organization relies on heavier decision making process for instance or stakeholders are not used to being extensively involved in project execution. . But overall I would recommend to use common sense and not to stick to rigid approach. Having something in between, if that seems to be the best fit for your project, is totally fine. Agile is not “fit to all” approach, it counts on certain maturity and strengths of your team. Saving Changes...
5 Pros - flexibilility, adaptability, popular with software developers hence easier recruitment, fast time to market for initial outputs, useful approach when all requirements are not clear,
5 Cons- upfront costs are uncertain, large testing workload, risk of longer overall duration, needs to fit with your organisation/senior managers need to understand it fully, complex development environments & release processes when multi teams involved Saving Changes...
