class ViewController: UIViewController {
NSMutableAttributedString * stringForLabel = [[NSMutableAttributedString alloc] initWithString: @"I accecpt the "];
NSMutableAttributedString * pPStr = [[NSMutableAttributedString alloc] initWithString: @"Privacy Policy"];
NSMutableAttributedString * and = [[NSMutableAttributedString alloc] initWithString: @" and "];
NSMutableAttributedString * tNCStr = [[NSMutableAttributedString alloc] initWithString: @"Terms and Conditions"];
[pPStr addAttribute: NSLinkAttributeName value: @"http://www.google.com" range: NSMakeRange(0, pPStr.length)];
[tNCStr addAttribute: NSLinkAttributeName value: @"http://www.yahoo.com" range: NSMakeRange(0, tNCStr.length)];
[stringForLabel appendAttributedString:pPStr];
[stringForLabel appendAttributedString:and];
[stringForLabel appendAttributedString:tNCStr];
[stringForLabel addAttributes: @{NSFontAttributeName : [UIFont fontWithName:@"Helvetica" size:16.0]} range: NSMakeRange(0, stringForLabel.length)];
self.myTextView.attributedText = stringForLabel;
self.myTextView.linkTextAttributes = @{NSForegroundColorAttributeName:[UIColor redColor]};
This post describes the steps necessary for customising the Issue Types on your own instance of Jira. The Jira documentation on Atlassian’s own Confluence Wiki is very comprehensive but I found that it was a little verbose for each action and yet at the same time it doesn’t actually indicate the full set of steps you may need to go through in order to get everything working as you would expect.
When you plug your charger into your iPhone or iPad you get a little chime (or two short vibrations if it’s in silent mode) to let you know its connected.
You can activate that same chime on your MacBook when you connect your charger with one simple step.
Summary:
This sprint retrospective activity can be particularly useful when you feel your team is facing a lot of blockers/impediments. It helps teams identify the issues that they are facing and encourages them to develop a plan for tackling those issues.
Summary:
This is a version of the basic ‘Stop-Start-Continue’ sprint retrospective activity which can be used when there is a particular need to keep tight control over timings. Each step can be strictly time-boxed and you can adjust the time allotted in each section to suit your needs.
If someone is connected to the wifi but can’t remember the code to share with you (maybe they lost that little card with the details you need or perhaps the router with the password printed on it is hidden behind a pile of books etc) you can just run the commands below in Terminal (Mac) or Command Prompt (PC):
Mac:
security find-generic-password -wa YourWiFiNetworkNameHere
PC:
netsh wlan show profile name=YourWiFiNetworkNameHere key=clear
It’s important to let users know when something is happening in the background with your app.
There are a few ways of showing that something is going on such as pop-up messages and progress bars but quite often you will see a ‘spinner’ known as an Activity Indicator in iOS.
Summary:
This tool can actually be used to run any meeting but I’ve found it to be very suitable as a sprint retrospective activity. The activity is based on a tool described in Edward de Bono’s book Six Thinking Hats. This is a parallel thinking process designed for effective group discussion and individual thinking. I saw Edward de Bono deliver a keynote presentation at the Learning Technologies conference in London a few years ago and had used the ‘Six Hats’ technique a number of times in meetings before trying to use it in a sprint retrospective.
Everyone likes feeling like they have a choice but how much choice is too much? Nowadays we have simply too much to choose from. Looking for a book? You can check out the iBooks Store or pick up your Kindle and there are millions of titles to choose from.
How many times have you said, thought or heard the words “There’s just too much to choose from”?
Psychologists call this the ‘Paradox of Choice’. In his book of the same title, Barry Schwartz explains that an abundance of choice leads to an inner paralysis, poorer decisions and discontent.
Summary:
This sprint retrospective activity is a fun way of identifying a team’s strengths and weaknesses and is based on the ‘Cool Wall’ segment of the the TV show ‘Top Gear’. In this activity, various aspects of a scrum team’s practices are presented by the scrum master and the team vote on how ‘cool’ they feel they are when it comes to that specific topic.