Working with process development, I have found that I draw on the lessons I learned in business continuity planning during my studies. In particular, I have found that the actions to take in response to risks, also known as the four t’s, has been particularly useful. These four are:
I’ve had a number of posts drawing on the experiences from my bachelor studies, that I started some six years ago. I’m currently studying what will be the final module, focusing on entrepreneurship, innovation, and sustainability. This has led me to think about the differences between intrapreneurship and entrepreneurship – which can be summed up as whether you’re engaging in innovation and change within an existing business (intrapreneurship) or in a newly formed venture (entrepreneurship). In the extension of this, I’ve also been reflecting a lot about company culture.
When running a project, its ultimate success or failure can only be defined when measured against predefined goals and objectives. Definition of these takes place during the planning phase of the project. It is imperative that these goals be SMART. By that I mean:
In Project Management, we talk about the Tuckman model, also known as Tuckman’s stages of group development. Though of particular importance in project management, the stages bear some relation to most aspects of working life. I think most of us would benefit from knowing the basics of it, and how it all works. Originally proposed with four stages in 1965, the fifth stage was added in 1977. The stages are, in order:
Roughly put, we can say that all projects must deliver:
My journey towards a Bachelors degree continues, now with the OU Module M258 (IT Project and Service Management). As I continue to study the module, I will write down my thoughts on various subjects. Like with my first module, TU100, these will all be collected under a category for easy reference. This time, unsurprisingly, the category will be M258.
These days, I am making my first serious foray into the world of Project Management, as I am studying the Open University’s module M258 (IT Project and Service Management). From working with the first chapter of our assigned text book I have gleaned the following three ways to look at the stages of a (software) project:
The basic overview
In Sense, you can reference a list to control what your program does. By default, the [line X from_file “file.txt”] references the Sense project folder, but it can reference one…
As part of my studies, I have been “programming” in Sense, a version of Scratch, the graphic programming environment developed at MIT. The programs developed in Sense are stored as .sb-files. Now, the problem is that these files are only readable by the program that made them (and Sense programs are apparently not readable by Scratch). The problem this poses is that I can’t be assured of being able to read the files when, at some point in the future, I might want to.
Luckily, Sense, and presumably Scratch, too, has an export facility, allowing you to export the program you’ve made to clear text. Here’s how:
As part of my studies, I came across this video. I’ve seen it before, and I’m sure many others have, too (right now, it has over one and a half million views on YouTube). Still, it poses some interesting questions, and looks at text in a different way.
As part of preparing to study at the Open University, I decided that I needed to establish some routines and generally speaking get to a point where taking an hour…