This is the second post in a series of thought experiments on applying Lean/Agile principles to the early shaping stages of a programme. Here I am using “programme” in the widest sense – to borrow a definition from MSP20071 “a temporary, flexible, organisation created to coordinate, direct and oversee the implementation of a set of related projects and activities in order to deliver outcomes and benefits related to the organisation’s strategic objectives”.
This is the first of a number of exploratory posts to express and refine my thinking on the subject. I want to pull together a selection of experiences with programme shaping by looking at them through the filter of lean/agile theory. Traditionally programme management, especially in public sector, is heavily influenced by stage gates. Having said that, the authors of more recent methodologies (e.g. MSP 20071) recognise the need for iteration and conceived a “transformational flow” of work that delivers benefits over time.
I’ve mentioned in previous posts (1, 2, 3, 4) that I’ve been having a small play with Iceberg, the workflow automation system from Fractis. Their tagline is “Build Workflow Powered Applications Without Coding”, an appealing concept to many. So how well do I think they have achieved it? In terms of relatively straightforward applications, the platform is certainly capable of a fast development of data, forms and processes, as evidenced by the growing list of sample applications, and for many cases, especially in smaller businesses, or small teams, that may be enough to get some real benefit.
I’m trying out Iceberg, the workflow automation platform. In previous posts I described adding some basic forms, views and processes in the context of a sample application. Today I’ve been experimenting with the security model. It seems both complex and powerful, with the downside that the online help seems to be only 25% populated in this area. Here’s what I’ve been able to work out: Access Control lists (ACL) – every object (optionally) has an ACL which can control Browse, Read, Write, Delete, Change Owner and Change Permissions rights.
I’m trying out Iceberg, the workflow automation platform. In my last post I described starting to build an application, based on this outline specification. I had just got to the point of trying to meet the first acceptance criterion on the first user story (all Project Issues must be uniquely identifiable) when I came to a grinding halt. The line I started pursuing was to have some kind of global object in which I could store the last used value for a ProjectIssue.
I’m trying out Iceberg, the workflow automation platform. In my previous post I decided what application I was going to build, and wrote the first two user stories. Again, I’m using the Iceberg User Guide to guide me. The first thing that is quite confusing is that the environment within which you are building your application is also the one which displays it – I’m guessing that a later stage creating user-only logins allows you to hide all the configuration options.
I’m trying out Iceberg, the workflow automation platform. Having successfuly installed the platform on my laptop I want to start building something. Of course, the two key questions before building any software (assuming the “Why?” in this case) are “What?” and “How?”. For the “How?”, Iceberg provide a good overview on their support pages, which in essence boils down to: Create the application Create the business objects Create relationships between objects Create forms Create views Add behaviour and workflow Security and permissions Connectivity For the “What?
As mentioned in my last post, I’m trying out Iceberg. Iceberg offer an “all in one” installer using the Cassini webserver, or for more complex installs you can download a zip file with the web application and a configuration script. As I already have SQLExpress and IIS7 in my laptop I chose the latter. The setup instructions are very clear, and follow the normal pattern – set up a database and database user, install the web application to a virtual directory on the web server, make sure all users and permissions are correct,
This Read/Write Web article led me to Iceberg, a product from Irish company Fractis which aims to make it possible for non-programmers to rapidly assemble business workflow applications. The applicationn, now at version 2.1, is based on ASP.NET and SQL Server, and is available as a free download. Licensing is free for non-profits or for up to 5 business users. A hosted version is available starting at $40/month for up to 5 users.
As I touched on in my last post, I am currently recuperating from an operation on a toe. The constraints I have are that I have to keep my foot elevated as much as possible, am confined to the house, and when I do stand or walk I have to wear a special shoe to keep me from applying any weight to the fore part of my foot and to protect the protuding K-wire.