Register  |  Login

On this page you’ll find the brief summaries for each of the key features mentioned on the SmartMethod home page:


       Agile specification, incremental build

Light-weight on UseCases, strong on interfaces and data models, the SmartMethod ensures you can be lean on documentation, yet create early validation (right product) to minimise unnecessary preventable change. In short steps, incrementally refine scope, estimates, and plans, to revalidate cost benefits and limit investment if it no longer makes business sense to continue. In doing so, the SmartMethod helps you maximize value for available budget.


       Facilitates a smooth transition away from waterfall

see Waterfall habits kicked.


       CMMI level 3 compliant process “out of the box”

The SmartMethod spells out all CMMI level 2 and 3 practices in verbatim format, by workflow. Thereby all staff have access to what CMMI actually means and states in practice. Thus people gain clear instruction on what’s needed to deliver at a CMMI level 3 time / cost maturity level. At the same time it is packaged in such a way that you don’t have to drown in it, by providing page-paths (starter, master, expert, by roles, etc) to incrementally extend you knowledge.


       Deliverable and practices -focused (rather than role-based)

Since its inception in 2002, this instruction approach has proven to work extremely well and facilitates easy adoption. With a deliverable focus, the team very quickly understands what is expected. In contrast, in a roles-based explanation system like that of the RUP or MS-TFS, one is always in the dark what to collectively aim for. It is interesting to note that in 2007 Ivar Jacobson, one of the fathers of RUP, also has adopted a practices focus for their new EssUP method (in their words “to fix some of the shortcomings in RUP”)


       Right‑sizing (tailoring) enforced

The SmartMethod has a Right‑sizing tool to scale the deliverables in view of team size, risk and type (the larger the team, the more you need to communicate and capture). As the project unfolds, you can upscale again, if needed. For more information on Right‑sizing click here.


       Aligns with ITIL

Few software development processes consider what happens at the end of the project, when the software needs to go into production. The SmartMethod ensures the project engages with IT operations already during the planning / elaboration phase, so that their ITIL change and release management can assess impacts, and cost and plan accordingly. The Method provides guides on the essential information which needs to be exchanged with IT operations to ensure a smooth transition into production (effectively a standard for the interface between the two).


       Aligns with PMBOK / PRINCE2

Alignment is achieved through the WBS, phasing, and risk, change and procurement management processes. The CMMI level 2 and 3 practices tighten-up the PMBOK for software development specifics and plug some holes in PRINCE2 (e.g. vendor management, scope and estimation).


       Can be used with MS-office only, or any mix of tools

The SmartMethod does not require any specific tools. If you do have them that’s great, but it can work with just MS-Office and shared drives. If you have efficiency tools like requirements management, design, automated testing etc then these replace the MS‑Office templates of the SmartMethod. Thus you can grow from no tools to completely integrated toolsets without having to change the process of development (SmartMethod).


 mail to colleague


Your Rating: 0.0   Average Rating: 0   Ratings: 0
Site Software v2.2.0, 26 Oct 2016