IFD environment..sounds familiar rite..but it really creates panic when it comes to its installation...a whole list of steps and bla bla...Thanks to microsoft for the IFD tool which really has made IFD installation really cool:)...
So now to get an IFD Environment up and running,u just need to install MSCRM4.0 like a normal on-premise MSCRM and then run the tool..Some dns setting needed ofcourse like adding an alias...and adding an alias or host for each organization in case of multiorg scenarios..In this blog basically i would just tell the setting for accessing your MSCRM4.0 through URL from ur base machine or anywhere outside the main server machine..For that just you need to follow following steps:
1.Go to C:\WINDOWS\system32\drivers\etc
2.Open the hosts file in a notepad
2.Add the key : [IpAddress] [OrgName].[DomainName]
But be very careful guys while you manipulate it because a wrong entry may screw up your machine...
So guys ready to use IFD ....:)
I have been fortunate enough to work with a team where Scrum methodology of Agile was followed religiously...Thanks to my 1st Project:)..Since Agile is too vast a topic to cover i would just cover in brief the phases starting from planning till acceptance....So the various phases which i would cover here are:-
1. Sprint planning
2. Scrum meeting
3. Development+Testing
4. Final acceptance
5. Retrospective
1.SPRINT PLANING MEETING:-In this phases the estimates for all the items scheduled to be covered in the sprint are estimated in Tshirt Sizes or in Story Points
2.SCRUM MEETING:-Everyday we used to have a scrum meeting where basically three point where discussed a.What was done yesterday?b.What we will do today?c.Hindrance if any?
The participant of this meeting will be developers,testers,leads considered as Pigs because they will actually be involved in the completion of work item..Others like managers,Customer etc are considered as Chickens..who can also be part of this meeting but they are not supposed to speak ..
3.DEVELOPMENT+TESTING:In Agile developers and testers go hand in hand.By the time devs are done with coding testers are supposed to be ready with test cases and then the phase of testing and bug fixing goes...Any task in not considered as complete till the QA marks it as closed...And its the responsibility of the dev to make sure his task is completed..
4.FINAL ACCEPTANCE:After the features or the fixed issues are closed it is being sent to the client for his final acceptance.The client tests it and gives his feedback on that...When the client gives a green signal then only the task is finally closed and marked as Accepted.Once it is accepted then only it is considered as successful completion of the iteration else it goes for Spill Over and gets added to Product Backlog
5. RESTROSPECTIVE:After end of every iteration or release there is an retrospective meeting where we discuss basically four points...a.What went good?b.What went wrong?c.Things that can be improved?d.Appreciation - Dont forget its required to boost the moral of your team..Helps a lot and makes people feel important...Nd guys nyways it doesn't cost your pocket so why to be miser in this;)...
Many of the terminology which i have used marked in bold may sound new to you..but if i cover all these in details then trust me you will feel bugged..So you can get back to me for any questions you have and i think i should be able to answer it......I love Agile and I think once you follow even you would love it:)..just try it out....
