Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

ADePT

2 replies [Last post]
Darren Kosa
User offline. Last seen 7 years 9 weeks ago. Offline
Joined: 8 Feb 2008
Posts: 256
Groups: None
Planners,

As someone who is always on the lookout to explore new planning ground, I’m hoping to build on David Bordoli’s post in this thread (and a number of other threads after doing a little forum searching).

I have a question about ADePT (Analytical Design Planning Technique) more specifically what are the differences between ADePT and Agile?

I’m more familiar with Agile development and as far as I can tell they both seem to promote incremental and iterative development over the traditional waterfall approach.

However, whereas Agile focuses on short, sharp timeboxed deliverables and is extremely adaptable when requirements change at any time during the project lifecycle, ADePT is aimed at the development and design phases and after this is complete traditional planning takes over. Is this correct?

So apart from the obvious IT vs construction and lifecycle vs phase, are there any other particularities that set them apart?

Regards,

Darren

Replies

John Steele
User offline. Last seen 13 years 24 weeks ago. Offline
Joined: 28 Oct 2006
Posts: 6
Groups: None

Darren, It has been a while since this posting was made but an outline of ADePT (methodology and software) has been uploaded on the WIKI - under 'planning software'. This will answer some of your questions.

In essence, however, the iterations that are identified through modelling the integrated process in the ADePT Design Builder application are not influenced by time (otherwise the iterations could not be analysed as they have embedded backward flowing logic) - they are simply information dependencies and interdependencies between activities. To enable two-way synchronisation with existing planning tools (CPM-based) a 'filter' has been developed that captures backward flowing logic at the interface between the tools and converts the data to enable scheduling using CPM (iterations included but represented as periods of parallel working).

This data, in combination with the backward flowing logic (which is retained in the ADePT software) enables 'lean' principles to be applied - basically, production control principles adapted to take account of the fact that an iterative loop is never 'made ready' in true production control terms. The ongoing use of the ADePT Design Manager application (sister product to the ADePT Design Builder) enables development of further detail as the process progresses, gaining commitments from those responsible, and identifying / removing constraints ahead of them creating delay is founded in lean and is a pre-cursor for agile. As such, there are great parallels between ADePT and Agile. 

John Steele
User offline. Last seen 13 years 24 weeks ago. Offline
Joined: 28 Oct 2006
Posts: 6
Groups: None

Futher on information on ADePT and Design Management can be found, videos of the application in use, and a downloadable trial version of the software can be found at: www.adeptmanagement.com