Showing posts with label Week 5. Show all posts
Showing posts with label Week 5. Show all posts

Monday, 19 October 2015

[Assignment] IONA case 2

Shane Errity, Nile Niall Yelverton and I list our findings, using the jump processes for Iona Case 2. The second half of the blog post outlines our solutions to the three key issues that we raised.

Issues:


Organisation Structure:
Business Model
 → Changed from people focused to product focused
Culture
 → Tight knit to dispersed teams (in different locations)
 → Culture of Wine and Cheese and informal Toners meetings, vanished.
 → ORBIX seen as a dead end job


ORBIX Focused:
Didn’t have a holistic view of  the company's lifecycle. (Racconn Chaos lifecycle paper)
Focused on a narrow viewpoint of just ORBIX didn’t consider how it interacted with everything else in the company.
 → This led to a cannibalism in profits
People in the company didn’t have a holistic view of the organisation, this can be seen by the quotes at the end of the Iona case 2. The Travelling Salesman example in Racconn paper, highlights how decisions are easily made if someone has all the information.


Expansion Strategy:
Linear approach to cope with a non-linear problem.
 → Orbix hired new people. Fredrick Brooks would argue this adds to the delay of the project.
 → On Call rota for engineers
 → Hiring more people only eroded profits
ART was the solution, it just  didn’t arrive soon enough
 → Every employee wanted to be working on the cutting edge of software, this made working on ORBIX seem like a dead end job, this added to engineer stress


Solutions:




Organisation Structure:
If IONA had a formal business model from the start, then the engineers would have been able to handle the quick expansion better.


ORBIX Focused:
Employees need to see/be thought the holistic view of the software development lifecycle and the ART expansion. Engineers wanted to be at the cutting edge and they didn’t realise the importance of their work with ORBIX to help ART succeed. They only had a narrow view that working with ORBIX was a ‘dead end job’


Expansion Strategy:
To cope with expansion, Iona should have changed the Orbix architecture towards a new technology paradigm, such as a service oriented architecture.

Sunday, 11 October 2015

[Homework] Project Requirements Week 5

Find an example of a real world project requirement?


This was the question posed to the class by our lecturer at the end of class, otherwise more commonly known as homework :). 
  1. I began my research by first asking the question, what is a project requirement?. I was trying to determine what were the essential components of a good project requirement.  
  2. I finally had a 'simplified' list of what I believed to be a good project requirement.  
  3. I then set about finding a real world example, which I could use in class discussion, or during the class stand up meeting. 
  4. The real life example I found was a project requirement for the library of Syracuse University (New York). 

The project requirement; 'The library will have a public-facing blog that will serve to communicate library news, events and resources, as well as providing the library’s user community with the ability to comment on posts.' (Syracuse University, (2011) 
I have attached a PDF* of the project requirement for you to view. While it is not one page long, as requested, I think it's a good example of project requirements. 

You find the link to the Project Requirement HERE*. 

Additional Information: You can view the results of the project requirements HERE. 

Reflection: While I personally think this was a good project requirement example. I think the project would have benefited if some of the functional requirements were less ambiguous. I think the project requirements were good, but the overall execution was not of the same standard. I have linked the website above for your own analysis of their execution of project requirements. 
Any feedback and/or comments, are appreciated. 

*The PDF is the work of Syracuse University (2011) and not my work.