Cromulent Cloud conducts rigorous investigation into various subjects, develops outputs of a technical nature, and engineers solutions to problems we have identified or been told about.
Findings subject to revision. Scope of work negotiable. Not responsible for implications.
Our work spans several areas we have organized into the following categories for the purpose of having categories.
We take existing knowledge and apply it to specific situations, generating new knowledge that can itself be applied to future situations. The cycle continues.
Using established principles from the field of engineering, our engineers engineer things. The things are engineered to a satisfactory standard by the time we're done.
We develop ideas, systems, and artifacts from a less developed state into a more developed state. This is done iteratively, or sometimes all at once near a deadline.
Data, systems, and situations are examined carefully by people who know how to examine things. A written summary is produced. Occasionally it changes something.
Before a thing is fully made, we make a less-final version of it to see if the idea holds. The prototype is sometimes mistaken for the final product. We are working on this.
We share our opinions with organizations who would like opinions from outside their organization. Our opinions are informed by experience and also by having opinions.
Our methodology is fully agile, which means we do things in a flexible order and call the results intentional. We have a board. Items move across it.
A preparatory sprint in which no sprint work occurs. We use this time to plan the sprints, name the sprints, and have a brief disagreement about whether sprint zero counts as a sprint. It does not.
We discover things, then rediscover them slightly differently two weeks later. By sprint four we have a nuanced understanding of what we should have asked in the kickoff. This is considered normal.
Stakeholders are convened and their conflicting priorities are written on a shared document where they will remain, visibly unresolved, for the duration of the engagement. Alignment is declared anyway.
Things are delivered on a rolling basis so that feedback can be incorporated before anyone has read the previous thing. Velocity increases until it is used as evidence that more meetings are working.
At some point the requirements will change. We don't know when or why, but we have designed everything so that when someone says "actually—" we can nod slowly and say we anticipated this.
A blameless retrospective is held. Blame is distributed evenly across the process, which is blameless, leaving no one to blame. Learnings are documented in a place no one will check. We scale.
We are also conversant in the following:
Statements made by real individuals, reproduced with their knowledge, about work that occurred.
We brought them in to look into a thing and they came back with a report. The report had conclusions in it. We implemented two of them and one of them worked.
I wasn't sure what they were going to do when we engaged them, and I'm still not entirely sure what they did, but the situation is measurably better now than it was before.
Their team used terminology I recognized from the field, which gave me confidence. Their final deliverable was a document and also a second, shorter document summarizing the first.
We offer several modes of engagement, each corresponding to a different level of involvement from both parties.
We are available to research, develop, and engineer things on your behalf. Reach out and describe what you have in mind. We will respond with a description of what we could do about it.