Pokazywanie postów oznaczonych etykietą software house. Pokaż wszystkie posty
Pokazywanie postów oznaczonych etykietą software house. Pokaż wszystkie posty

środa, 2 stycznia 2008

Sources of knowledge

Mood: Just after straight-11 free days without ANY business phone call (can you imagine that?)
Link: Odd Christmas wishes

I have got some time ago the very good question: "Where from do I know, what I know?". I am the type of the guy, who asked about non expected thing, usually can not come up quickly with a clever answer, so I answer something not-clever-enough. The problem is that, this type of things keep staying in the darkness of my mind for some clever-enough story. The worst of all, the dark side of the soul wakes up usually 5' after I should be already sleeping and once per a while instead of behaving like the 31 years old man should behave I get to the laptop and write something like right now (tommorow morning will be truely a horrible intiation of the new year ;) ).


Anyway... lets do the home work.


I am the type of the guy who does not like to go to the courses, which I usually very expensive, time-consuming, borning and not-engouh related with the real life. This is way I usually prefer some self-pace paths, where books and web materials are the best, primary friends. In case of Microsoft certificates (MCSD.Net) I also convinced my boss to buy the examination training kit from Transcender (wow! they have a new web page) and I was very satisfied from it. I always focus myself and my subordinates to focus on some certificate. It is not to be some type of a label whore, who needs to have a jeans from Wrangler in order to feel better, but having a material goal is always a good motivator and the one, which you can set in time - usually the certain date and hour of the exam, when you shake like the leaves on a tree in autumn. Anyway I am crossing my fingers for you ;) and I give you one hint...


If you fails, there is always a possiblity to have a next shoot. I remember until today one exam at my university, when I had three make-ups; the most horrible was that each time I have spend doubled amount of time over the books and the result was doubled misrable :D The professor Jan Węglarz finally gave me the lowest possible note to pass, just to get my out of the range of his sight. Staying in front of him I truely considered to refuse the offer despite my desprate situation, but as usually my opprotunistic side has won ;) EVERYBODY has at least one story of this type - you must to set up and take a challenge.


The second and more interesting source of knowledge are people. There are two main figures who have been the sources and spiritus movens (surprsingly I could not find yet the english explanation of these latin words). One of them is positive and second one is rather negative.


The first one, was Clem Predergast who rather acts than publish and this why there is nothing about him on the web. He was though the one, true manager whom I met and whom I could watch managing and leading the people in software projects. It was more about the soft skills and possibility to motivate people in right direction, but there was also about the "know-how" import from Irish island and Performix company. How the support mechanisms works, how QA labs should look like, what road show is about, where there is a sense to pump the money and how to gain the support from executives. He had tones of his phresals, which I am sure, most of people who have worked with him, will remember for a long time like "all hands on pump". I keep catching myself on repeating them or doing some small things in the same why how he did it like learning first how "cool" and "shit" sound in foreign language, when I am in one these countries where german and english is not the mother tongue. Learning by the example is definitely the best possible method.


The second person is much more interesting and I have been growing up with this feeling for years. This person had probably better hard skills than I had on each, technical level - starting from code, through the architecture and finshing at methodologies knowledge (especially the agile once). I am quite sure that he still has these skills better, but he had some problems with soft skills. Unfortunatelly it has appeared after some time that we do not work together but against. Why I come up the situation? Because he was a perfect challenge, which (or rather who), I admit publically in this new 2008 year, still sits in my mind and keep challenge me in the ares, which about we had this short, usually intense discussions. Of course that is not my main or even secondary motivator, but for example it forces me to review once per a while all the existing methodologies and only the ones, which I prefer or can be useful.


Where books can be treated as hardware, people would be the software - you need both and you need to have some balance. You need to have hardware to load software, you should not have too much software on the weak machine and the most important... do you really need Vista? :D

czwartek, 15 listopada 2007

fxCop story

It is quite often, that companies posses their own “Rules of coding” document like the one from Philips, which is more or less the compilation of documents available on the net. I strongly suggest also reading "Framework Design Guidelines", which is my bible in the area. One thing is to write the paper and the other is to have it truly implemented. Some companies have the process established that none code may be checked into repository without the code review performed by the other developer, but that is open issue is if this process ensures that all rules are always followed and exceptions from obeying rules are registered. That is why, it is always nice to have the cyber cop, who will check once per a while if codes in your repository follows the rules established in written documents. The cop has even a name on this t-shirt and heeeeeaaaaar heeeeee issss - fxCop.

Each project is different and each time you must select, which rules will be used. I think that the best way to deal with the issue is the following:

1. Create fxCop project
Get all dlls and exes which will be analyzed and add them in target section. Analyze them and save the whole project.

2. Filter sets of rulesFor example, if you are not planning to localize your software you do not need Globalization Rules at all. In similar way, if you do not have the legacy problem, you probably do not need the Interoperability Rules.

3. Filter rules
Check each rule. More errors is in rule, in more details you need to analyze what exactly the rule is about. In some situation fxCop provides you the link directly, in other situations you must look at help or ask MSDN manually about the rule. You will find quickly that some rules are useless for you like (for me):

  • EnumsShouldHaveZeroValue – we use enums just internally and they are not public
  • AvoidNamespacesWithFewTypes – the project is at early stage and further extensions are planned shortly
  • MarkAssembliesWithClsCompliant – we do not need to be compliant with CLS

And some of them are golden one (for me):

  • IdentifiersShouldBeCasedCorrectly – priceless thing, which usually would take me a lot of time, if performed manually
  • AvoidUncalledPrivateCode – it helps me to find quickly unused code
  • DoNotCallPropertiesThatCloneValuesInLoops – it never should happen

Except checking MSDN, if that is necessary open the code and check where particular error happens in code. It will happen often that only looking at code, you can answer if the problem is dummy or real.

Analyze the code again and check how much work there is to standardize the code. If there is too much, than you can afford you need to repeat step 2 and 3. If you can, talk with your developers to ensure, that your point of view is valid.

4. Look at errors sets and ensure, that they are valid
Forget for a second about fxCop and how cool it is and try to put yourself in developers shoes. Are enlisted errors really important; do they really need to spend a time and risk the repair (which may cause additional errors)? Remember that you should implement the whole thing incrementally to convince people that it truly empowers they work. If you start with too many rules at the beginning, you will cause people to make refactoring for months, what will not make them and your boss happy ;) That is why, it is good to “thing big and start small”.

Filter the last time, the list of suggestions for developers.

5. Establish the process
The tests have been performed for the solution, which consists of 62 projects and has around 30k LOC.

Option A
Run the report from command line manually. The default xml report is parsed nicely by default by IE – options like expand/collapse are possible there without any configuration. You may generate the CSV in the same way, but in fact that is the same xml (just extension changes). The disadvantage is that you need to run the whole process manually and you need also to update the list of targets as the outputs (dis)appears, but the plus is that it does not disturb the daily work of developers. The batch like:

fxcopcmd /p:"..\..\..\_fxCop\ESPO1v0.FxCop" /c /o:".\FxCopReport.xml"

Took me about 1:21.

Option B
The other idea is to apply the fxCop process as after build for Release version of the product (“Adding FxCopCmd to Your Build Process”). In this way, daily Debug builds are quick and when everything is ready key developer does Release build and gets immediately the report of things to repair. Unfortunately post-build actions are available on the projects level and not on solution level, so you must either apply it to each project separately or once to project, which is build at last in the whole solution, if you are sure it will be always compiled as last one (Project Build Order). In this case, you must be also sure that each person:

  • Has fxCop installed
  • It is installed at the same place or path is set properly
  • fxCop project is downloaded into the same place at each PC (shared folder possible)

FxCopCmd /p:"D:\SVN\ESPO\fxCop\ESPO.FxCop" /c /o:"D:\SVN\ESPO\fxCop\FxCopReport.xml"

The other option suggested in here is to use the VS 2005 add-in and link it with MSBuild process.

Option C
Even more interesting option is to add the action as a post-build in any project. You need to change the fxCop project and clean Targets tab. You may establish that folder, where fxCop has been installed is added to the Path global variable and common folder with fxCop project and where all the reports will be stored. You need then to ensure that post-action is added to each project to have the whole thing working

Fxcopcmd /f:"$(TargetPath)" /p:"..\..\..\_fxCop\ESPO1v0.FxCop" /c /out:"..\..\..\_fxCop\$(ProjectName)-fxCopReport.xml"

You need to know, that my sample solution has compiled in 32-45 seconds without fxCop and in 8:10 with fxCop for option C (even when just 5 rule sets were turned on)! Only iIf you don’t have too many projects, it may be the good option. In other cases option A or B, will be probably better.

Whichever option you chose, there has to be some negotiation stage (especially at the beginning until the set of used rules will not stabilize), when developers may give the opinion about the usability of the particular rule or changes. When it is established and the set of rules is redefined, it must be double checked after some time if the errors are repaired

You may also consider at later stage to write your, customized rules, but you always must consider if it really safes time ;)

Conclusion
You must spend some real piece of time to make the whole thing to be REAL, but I have a strong believe that the automated effect is usually worth of it especially if you the project is:

  • long term
  • open source or you need to pass the rights to source codes somebody else
  • the code is analyzed externally
  • to which the others may write plug-ins
  • developers switches

Of course you must review the whole thing once per while and redefine the set of used rules (make the tolerance more narrow or wide), but the even the knowledge about the post-build process will motivate developers to write better code.

At least, but not at last that is important to mark, that automated process is just the support and not replacement for manual code reviews.

sobota, 10 listopada 2007

Marriage of Prince2 with Microsoft Solution Framework

Very often there pop-ups the question like: 'What of methodologies do you know/use?'. There is usually some smart answer like PMBoK, RUP or SCRUM, but when the question is drilled down, it appears out of the blue that there is just the set of unique practices - the mixed salad from everything what market offers and world wide web says about. There is nothing wrong with it and furthermore it is a wise strategy to collect patiently the practices, which truely works. Wise senior executives will slow down the saint paladins, who coming back from the training are trying to change the whole company into the Six Sigma or whatever else. Of course this type of change is possible, but it must be implemented incrementally and it must respect existing well-working practices, even if they do not fit to the template.

For a long period of time I have been using (or I have tried to use) the MSF and I am quite used to it. Of course, there had to be some compromises each time and it was never the pure implementation. For example just once I had the situation where there was the true separation of the project and product manager roles.

Nevertheless at my current position, there is a strong rule across the whole department to use the Prince2 methodology. This type of situation, common and strong support from top executives, does not happen often. I am currently on my learning curve of the methodology and I must admit that only things, which you do not know scares you. Furthermore, it seems to be a good fit to treat a Prince2 as a general flow of documents on higher, execuitve level, where written documents are necessary to take some serious, strategic decisions and MSF as a parallel, technological flow on a tactical level.

The main flow of the Prince2 is more-or-less as follows:
  • [DOC] Project Mandate
  • [PROC] Starting up a project (SU)
  • [DOC] Project brief
  • [PROC] Directing a project (DP)
  • [PROC] Initiating a project (IP)
  • [DOC] Project Initiation Document
  • [PROC] Directing a project (DP)
  • Stages after stage
  • [PROC] Closing a project (CP)
  • [DOC] End Project Report

DOC : Document
PROC : Process

DP is mostly about decisions of a steering committee : 'do we continue a project or not?'
There can be any number of stages, one after the other

Stage is in fact the mixture of the four processes: Controlling a stage (SG), Planning (PL), Managing Product Deliver (MP) and Managing Stage Boundaries (SB), but to simpfly these things I called the thing Stage.

The Prince2 methodology definitely causes formalization of the project, but in case of a big nterprises that is actually a good approach especially at the beginning and at the end. After the key decision is taken each stage of the project may be passed to MSF solution, where we already have the Vision phase managed and there is a time for all the remaining 4 phases – planning, development, stabilization and implementation. These are strongly technical activities, which are not in scope of Prince2. The best sample is a planning phase, which has totally different meaning. In Prince2 that is about the way how the plan is constructed: what will be delivered (products), what are the linkages between products, risk management, estimation and master plan. In MSF it should be actually called design and that is splitted on conceptual and technical planning of the architecture.


At the end of the whole project the deliverables (work packages) provided by MSF, should be checked within the Prince2 Controlling A Stage (SG) process or Closing a project (CP). This double checks that final result goes along with expected and defined within Project Initiation Document.

Assuming the business case of the big company A, which request the delivery of the big software product X and a smaller company B, which is a pure software house. The company A may use Prince2 and company B the MSF, without bigger problems in communication. Actually Prince2 itself predicts that company B may use different methodology (not Prince2) and it is a main purpose of the whole Managing Products Delivery (MP) process.

Furthermore the whole concept is not new, when we speak about Prince2 and RUP (I really found the link after writing the first version of this document) ;)

piątek, 5 października 2007

Advanced Project Management- Herold Kerzner

Mood: Sick
Soundtrack: Relax and take it easy (video clip is horrible, so this is why I prefer to display just cover :))

The book is definitely the must to read for any manager or leader in middle size or big organization (not only from IT sector). It is very visible, that the author put the strong effort in collecting the experiences from big number of companies. It is a pity that number of companies did approve publishing, but the list of contributors is very impressive anyway and it includes the brands like Sun, CA (all their procedures are published in appendix D! p733), HP, Nortel, Erricson and ABB. Sometimes the author allows treating the pages of his book as the free commercial for these companies, but usually the valuable information is passed including even some sample forms. Each chapter is full of samples from real life of the company with sweat and pain scenarios (the second one usually under the cover) – that type of approach gives that book a special, unique taste. Usually that type of book is saying you in rounded words what should be done, but this book says you also how. It covers a very wide angle of topics starting from the document flow systems, organization structures and finishing at some aspects of corporate politic.

When you start to cooperate with some organization, your first step should be formal or informal analysis of the situation. There are some samples of self-surveys (p653) and strong input for preparation employee survey - case 5, appendix I (p787), but the most interesting is the 2nd chapter defining the 5 levels of project management culture:
• Embryonic
• Accepted by directorate
• Accepted by managers
• Growing
• Adult
There is number of samples, definitions and methodologies, but the most useful will be the appendix B and C, giving you ready to use surveys to find out, on what level your organization is. If you need some guidelines in the area, the part 5.14 (p.248) contains some auto commercial about the Kerzner tools used for such The Growing and Adult stage are also broken into the pieces within 5 levels of Project Management Maturity Model (p239)
• Common language
• Common processes
• One methodology
• Competitors analysis
• Constant improvement (nice checklist in chapter 14.7 – p. 600)

Chapter 4 is giving you number of interesting samples from various companies, which worked out their own methodologies basing often on PMBoK. Prince2 is mentioned much more rarely and it seems like just Sun use it (p676). It was also interesting to read that Sun created originally RUP methodology. Anyway, there are not many books, which are brave enough to say that there is no golden rule and each company must create their own methodology. The IT fellow will find some well-known spots like Microsoft’s MSF methodology (p160), but most of the samples are quite fresh. The CIGNA sample (p138) was very good showing very well the linkage between the process and project plan. Intel (p147) enlists in details how the magic happens in real life, focusing on the document management. The list of critical aspects, when creating the methodology (p146) is also very valuable, but the best is the DePICT methodology from Exel (p153). It was the only company brave enough to publish their own document templates. Bravo!

Except strict project management the book covers also the general organization management issues including the Project Portfolio Management in chapter 7. The most interesting were the processes of choosing the projects for realization and two matrixes at drawings 7.6 and 7.7 (p308).

The 8th chapter is about the Project Management Office. I must admit, it was the first time I see so good PMO portraiture. Definitely, each organization has different understanding of PMOs and it is presented in part 8.4, but list of duties (p.334) seems to be common for most of them. Again, the chapter shows the real life situations starting from project approval mechanism like the 3 level recommendation mechanism (p354), closing at the sample template of document, which closes the project (p340) and set of sample postmortem questions (p360). Unfortunately, the implementation of documents management systems, which is in PMO duties, is not covered. The only things, which can be found, are some general drawings in chapter 16 (16.4 p647 and 16.5 p648), which shows document libraries structures on intranet sites. It would be great to see more in the area.

Very often, the risk management is neglected and that is probably why the author creates the whole chapter 9 just about that. He treats it in the complex and process way (checklist at p402), gives great ABB potential risk list (p413) and Motorola’s risk management system (p428) plus focus strongly on change management (p418).

I mentioned about the politic at the beginning, even if the book does not mention the word. That is known, however that half of success is to know what to do and the other half is to find a way to implement the change. The book give you a lot of tips how to fight with the resistance against the change, which exists often in big companies. The book mentions the interesting change management preparation list (p 243) and cool “basket team” scenario (p443), which shows that there will be always the person, whom you will not be able to change. The whole chapter 11 is discussing how to win the directorate attention. The sponsor or sponsor committee institution seems to be the best for it and chapter 11.2 contains some nice proves for it (p483).

To avoid accusation for being paid for this review, I must also to say a couple of bad things about the book. In some moments the author is trying to prove that some periods in history was about some particular stages in organizations grow. It went too far and drawings like 1.3 (p23) saying e.g. that the year 1994 was about “Cost analysis of live cycle” is simply funny. This is invalid tone, which can be heard through the whole book. Luckily, it is not in the mainstream and it can be ignored. The other disadvantage is, that there are some moments where the book is just the flood of words like the chapter 12 treating about trainings. The book would be as good as it is without this chapter.

On the other hand, the book shows definitely how wide the topic is and sometimes the mechanisms are just mentioned without further description:
• Statement Of Work (p196) – part of scope management
• Work Breakdown Structure (p196) – tasks management
• S curve (p196) – cost management
• Responsibility Assignment Matrix (p197) – responsibility management
As book has already over 1000 pretty well used pages, there is no space for blaming the author. See just for a second how often have I used the words sample and “in practice” – it describes the best the content of the book.

Score: 5.5/6 (very good)

The numbers of pages are based on polish translation of the book and they may be different in english version.

poniedziałek, 23 lipca 2007

Software house

I have just published the definition of the software house at Wikipedia. Any suggestions highly appreaciated.
 
web metrics