My livejournal friend TheKonst has posted his interpretation of Scrum management technology:
Scrum incremental development - by Konst
Original:
Scrum incremental development - original
:-))
ПЕСНЬ МЕДВЕДА
однажды в студеную зимнюю пору,
я вышел из леса,
был сильный мороз.
дорога лежала моя к точприбору
инжоит совсем без меня бы замерз
Karina
====
MEDVED SONG
at winter once I came from forest
it was a very heavy frost
my way was laying to our office
without me - Injoit lost
translated into English by Taras
powered with Alexander S. Poushkine’s rhymes
One of our clients hasn’t been available for a chat this evening, being watching the inauguration ceremony of the new president of United States, Barak Obama. Other two cliens have even travelled to attend the event. I’ve also watched few minutes of it before going to my aikido class. This is important for us not only because we have many US-based clients - new president it is always a hope and as US plays a big role in all geopolitical processes in the world so let’s hope this event turns a page into a new better world starting with this new year 2009 where every one of us can show their good sides and realize their dreams. Congratulations USA, Barak Obama seems to be a good choice especially now when world economy requires some anti-crisis management!
Taras
Ah yes, I Googled for “outsource iphone” without the quotes, and your website was the 3rd result
- Tor Martin Kristiansen, one of our customers
UPD: while our checklist managed to help some people, I’ve found the most explicit manual on this issue written by Ralf Rottman so posting a link to it here so that you may check it too (it’s much longer than our checklist but it covers the topic 100%):
http://www.24100.net/2009/02/iphone-sdk-mobile-provisioning-0xe800003a-0xe8000001/
And this is another good and fun guide, thanks to this guy I stopped to bother about Provisional profile not showing up in my Targets settings list - apparently they have removed it in 2.2.1 !!
http://www.codza.com/how-to-fix-iphone-code-signing-errors
I’ve written this for one of our clients and the client managed to load the app onto his iPhone device successfuly. This being after studying the official Apple guides etc. So I’ve decided to publish our unofficial checklist here as this might be useful for others as well.
Sometimes people experience problems when publishing from their Xcode directly to their iPhone, or this issue might also arise when, as frequently in our case, developers are using one set of certificates and client, testing the app, uses their own certificate.
So, what you should have done to
check you did everything right to publish from your Xcode to your iPhone
in your apple developer web interface -
1. Added App ID
2. Added Device
3. Created certificates (1 private, 1 public, downloaded and added them to your keychain)
4. In Provisioning – added Profile
(specified your app id and device)
5. Downloaded the profile created.
In your Xcode
6. Added profile to the Organizer
7. In the project, go to Other resources / Resources and edit Info.plist – look for key “CFBundle Identifier”
replace its value with “YOUR ID”.* where “YOUR ID” taken from your apple web IDs – so if we have XXXXXXXX.com.injoit.appname, then we take XXXXXXXX and we make it:
before:
com.yourcompany.${PRODUCT_NAME:identifier}
after:
XXXXXXXX.*
In case getting any errors when publishing from XCode to iPhone, try disconnecting iPhone, relaunching both your iPhone and Xcode and trying again.
The whole procedure is described here:
http://developer.apple.com/iphone/manage/distribution/index.action
(Building your Application with Xcode for Distribution). Some steps in the guide (like setting Target) seem unnecessary and we can just publish w/o problems, just check you’ve done everything correctly in the web interface at Apple website, added your profile to the Organizer and also edit the .plist file.
Hope this helps.
Taras Filatov, CEO to Injoit.com.
Thanks to Vladimir who helped to write this checklist.
Choosing of the most effective and appropriate keywords and keyphrases is basic part of search engine marketing campaign, whether it is pay-per-click or search engine optimization.
First of all keywords might be relevant to the theme of page and there shouldn’t be too much of them.
Once you’ve determine all possible variants of keywords, you need to choose the most effective.
One of convinient methods of measurement of keywords competitiveness is comparing of their KEI - keyword effectiveness index. This method was first introduced by Sumantra Roi and now is used by some popular tools of keywords researching, such as Wordtracker and other. The formula of KEI is:
KEI = (P²/C), where KEI is the square of the popularity P of the keyword for 2 last month divided by its competitiveness C (the number of sites which search engine displays when you search for that keyword using exact match search).
Actually, there are some other variants of KEI formula:
- KEI = (P²*1000/C): P - popularity; C - number of competing sites in search engine for that keyphrase
- KEI = (P²/S): P - popularity; S - number of Google matches for “allintitle” for that keyphrase
- in Wordtracker KEI is a logarithmic scale from 1 up to 10. It is similar in principal to the Richter Scale, commonly used to measure earthquakes =)
- Instead of using 2 in KEI = (P²/C) formula, you can use any power of P greater than 1: the higher is the power of P in the formula, the higher will be the emphasis on popularity. We choose the 2nd power as a good balance between both popularity and competitiveness
So, how do we use KEI tool in our practice? First, we determine a target region for optimizing site and choose some most popular search engines for that region and target visitors. Then we calculate KEIs for each of those search engines and count an average KEI for each keyword. Researches for several search resources are necessary to get more accurate results.
There is a common rule for interpreting KEI results:
- less than 10 considered as poor keywords
- keywords above 10 - good keywords
- above 100 are excellent and should be used in your campaign
But there is always some “but”. In case of received KEI results, it is only a basic measurement, and you can also check the other important criteria such as getting Google Page Rank, the number of competing PPC ads on Google or Yahoo. There can be many reasons why KEI are showing you something unexpected: the most search engines don’t give the accurate number of pages in their index, the number of searchers isn’t an accurate number - in many times keywords popularity is inflated by the use of automated tools, etc.
So, you have to ask yourself: does this keyword have sense for my site and will it attract more users and convert them into clients. If your common sense tells you “yes” - don’t pay attention to possibly low KEI and use that keyword.
Make happy choice!
Being professional in links buying issues, we know where to find and buy links so that they help in the promotion of your website.
- We choose websites that are related to your topic and are well-respected.
- We use tools to monitor the inbound links you have and how they affect positioning of your website throughout time.
- All the dealing with website owners, links checking and price negotiation processes are fully automated.
- We write original and relevant texts for the links carefully choosing the keywords after specil research
These key principles ensure you get top positions in your required search requests niche while keeping the budget optimal.
One of the latest links buying achievement is the promotion of our iPhone development page at Injoit website - we’ve got 5th rankings in “iPhone outsourcing development” and “iPhone custom development” and 1st ranking in “iPhone outsourcing development” for local language settings.
Results for ”custom iPhone development” at google.com
Results for ”outsourcing iPhone development” at google.com
The results might slightly change by the time you’ll be reading this post.
4 of Injoit while travelling in the train after GDD
Use case (also known as user story in extreme programming) is one of the most effective ways to describe how particular system should behave when interacting with user in particular situation.
So use case is a great way to let us developers know how you think your system should work after the project is finished and it is implemented.
Along with designing mockups, writing use cases provides you with better understanding of the desired architecture and makes you think about things you couldn’t think of before. So this allows you to save time and money, shaping out your system’s architecture BEFORE development has started.
Another great thing about use cases is that they can easily be used as test cases when doing QA (quality assurance) of your work - testers just use them as a guide moving step by step and checking system’s functionality against it.
Typical user stories or use cases are step by step written examples of user-system interaction.
Traditionally each step starts with “User” or “System”, this is a rule for writing use cases.
Find below an example of a simple use case from one of our projects, this might help you to create them for your projects. You may find more about use cases in Google and Wikipedia.
1. System displays intro screen, “Start game”, “Options”, “About” buttons in the bottom (see mockup 1)
2. User touches “Options”
3. System displays options screen with buttons “10 Questions”, “1 Minute Test”, “3 Minute Speed Test”, the pre-selected option highlighted (see mockup 2)
4. System displays “Cancel” and “Ok” buttons (see mockup 2)
5. User touches “1 Minute Test”
6. System highlights “1 Minute Test”
7. User touches “Ok”
8. System returns to the Intro screen
Exception 1: No option pre-selected
1. System highlights “10 Questions”