“The only thing that is constant is change” ~Heraclitus
This proverb is often told to individuals (like me) who love to see a project follow a plan from start to finish. I’ll be honest, I’m a planner. I’m thrilled when the plans I put in motion actually work out the way I intended. These are the moments when I retort, “the only people who like change are wet babies.” However, more often than not, something changes, which throws off my entire plan and forces me to not only revisit Heraclitus’s proverb but also rethink my plan entirely.
Building software, particularly in Agile development, is no exception. In fact, the second principle of the Agile Manifesto states that developers should: “Welcom[e] changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.”
After one particularly difficult midterm in college, my professor said, "This is just a wakeup call; there's still time to improve before the final." I think that wakeup call was particularly painful, but my professor's words stick with me today, especially when thinking about data collection (or lack thereof) when a project is over.
I am often asked this question during SLIM Training classes. I remember wondering about that myself. It is a logical question since SLIM-Estimate workbooks are often imported into SLIM-Control to create the baseline project plan. The answer is ‐‐ they are not directly related, because uncertainty ranges, probability curves, and control bounds are designed to perform different tasks. This post is the first in a series looking at risk associated with an estimate, risk of your project plan, and handling deviations from the plan.
After being away from QSM and the software world for three years, I was blown away by SLIM v8.0's dynamic product integration. I knew it was coming, yet I was still impressed by the simplicity and power of analysis promoted by real-time data and tool links across the SLIM Suite that frees managers to focus on the important program issues.
SLIM-MasterPlan is the center of the SLIM Suite product integration. It improves upon previously existing program management features of aggregating multiple SLIM-Estimate projects and ancillary tasks with two new capabilities:
SLIM-Control support for Rational Collaborative Lifecycle Management V3 is validated as ‘Ready for IBM Rational’ software.
MCLEAN, Virginia – QSM, Inc., a leader in software and systems development estimation, planning, and project management, today announced that they have upgraded their integration of SLIM-Control to support IBM Rational Team Concert V3.0.1.
Rational Team Concert provides a unique team collaborative development environment enabling productivity and quality in modern software development. Project data in Team Concert, such as Work Items (stories planned; stories completed) and Quality (defects found; defects corrected) can be retrieved by QSM’s SLIM-Control to perform its project analysis:
As our clients expand into new design disciplines, QSM recognizes their need for estimation, tracking, and benchmarking tools for domains outside of just software. Our goal with SLIM 8.0 has been to increase configurability within our tools so our clients can model any type of system quickly and easily. With SLIM Suite 8.0g2, QSM continues to expand our offerings to support different design processes and increase ease of use.
SLIM Suite. An auto-update notification feature has been added to detect when a newer version of the SLIM Suite exists and is available for download. Enhancements have also been added so Export to PowerPoint now defaults to .pptx file format and Export to Word now defaults to .docx file format where appropriate.