Home » Posts tagged 'agile'
Tag Archives: agile
Recommended: learn basics of Agile risk management. It’s simple, free, but helpful.
- Google certified Cloud Architect ($139, 529 annually)
- PMP (PMI Project management professional) ($135,798)
- Certified ScrumMaster ($135,441)
- AWS certified solutions architect ($132,840)
- AWS certified developer ($130,369)
- Microsoft certified solutions expert (MCSE) ($121,288)
- ITIL Foundation ($120,566)
- Certified information security manager (CISM)($118,412)
- Certified in Risk and Information systems control (CRISC) ($117,395)
- Certified information systems security professional (CISSP) ($116,900)
The DevOps Agile skills association renewed the certification roadmap, and the 3rd tier (Leadership level) certifications are available now. I have passed the Product Owner certification one of the first, and want to share a brief experience about this prestigious certification.
The Product Owner role is a leading role to ensure the Product vision, roadmap and backlog, and finally the product value to a customer.
The DASA association actively drives training and certification activities in this area.
The PO certification exam includes 40 questions (in fact, not very complicated, especially if a candidate is good with Scrum and Agile). Each question is followed by 4 answer options, one of those is correct. 26 correct answers (65%) lead to success.
I passed the exam at the first attempt. It seems to me that the certification marks that junior PO is ready for his/her journey.
As any other certification it helps to structure candidate’s skills and practical experience.
We strictly follow the recommendations and feedbacks of our students. And now 3 practice assignments are added to the course.
Now each student can make his/her own exercises according to his/her IT organization specific features and discuss the case with the trainer at the course forum.
Learn about DevOps culture during 10 minutes!
(c) Vince Alcalde (11.28.2017):
“(Part Parody. Part Not. What a Die Hard Waterfall Enthusiasts’ Manifesto might Look like)
We have uncovered the better way of developing software by having done it and continuing to do it over many decades.
Through this work we have come to value:
Estimating over No Estimating
Scheduling over No Scheduling
Requirements over No Requirements
Big designs over No Designs
That is, because there is probably no value in the items on the right, we value the items on the left more.
Our highest priority is to satisfy the customer through delivery of valuable software on budget, on schedule, on spec.
Welcome changing requirements, even late in development. A change control process lets you weigh the cost of the change versus the benefits, so only cost-beneficial changes get through , saving you from yourself.
Deliver a working production software once at the end. There is no point in delivering half-baked bread – it won’t taste the same as the final product.
Business people and developers must work together throughout the project. (The Agile Manifesto did not invent this)
Run projects utilising motivated and expert individuals and teams. Give them the environment,schedule, budget, information, and support they need, and trust (and track) them to get the job done.
The most efficient and effective method of conveying information to and within a development team depends on the context.
Achievement of milestones and Earned Value are the primary measures of progress.
Waterfall processes promote sustainable development. The teams doing the actual work only work in one or two phases of the project, never all, so they don’t burn out.
Continuous attention to technical excellence and good design enhances non-turbulent flow of work.
Documentation – the art of recording information so it’s permanently available in the future – is essential.
The best architectures, requirements, and designs emerge from the best architects, analysts, and designers.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. (The Agile Manifesto did not invent this).”
Microsft(r) Project(r) Online new version contains Sprint tools, and Kanban boards for Agile teams. We suppose it’s a very valuable improvement for Agile oriented developers, virtual teams, and also for a large-scale projects. In a large project top-down planning is implemented in a waterfall manner, while packages are implemented by small agile teams.
The option is not available in a standard Microsoft Project in the Office package yet.
The PMI has announced the changes in PMP and other Project management certifications in connection with PMBOK Sixth is available since September, 6th.
The main change is a new chapter concerning project manager’s leadership skills: communication, team skills, business strategy understanding, and others.
Some updates concern new terminology and chapters renaming.
The exam update is announced in Q1 2018 with more strict date coming soon.