Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
For customer service week this year, I have the privileged task of creating a technology themed gift basket. I'm trying to keep the basket under $50 as I have a bluetooth keyboard/mouse combo that I'll be adding to it. Besides canned air and monitor wipes, are there any other recommendations for a PC based basket? I was thinking about a USB thumb drive and/or blank CD/DVD media. Any other ideas?
LED flashlights and multi-tools.
You can never have too many LED flashlights and multi-tools!
There is a risk it might push you over your budget, but I would definitely check out www.thinkgeek.com. They have a lot of very fun and off-the-wall gifts like caffeinated soap, fun t-shirts, pen drives, and the like.
If you are looking for gifts for a Help Desk / Customer Service rep, then any of these would be nice.
A remote electric shock device to buzz id10ts on the other end of the
phone.
A license to kill.
A recording of David Spade doing the no commercial for when callers get
put on hold.
(for the guys) High Quality pictures of Natalie Portman, Robin Page (http://www.simple-talk.com/author/robyn-page/) or Sarah Chipps (http://girldeveloper.com/)
I pretty much want everything from http://www.thinkgeek.com
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I am new to Scrum and I am trying to use it for website support and maintenance.
For website support and maintenance, we often receive small tasks, for example: replace a banner on homepage, change phone number on contact page, remove image xyz on article 123, etc... I don't know how to deal with these small tasks in Scrum.
At the moment, I create a single task in backlog, and a single Sprint for each task. Then, execute each task individually. Am I right?
In Scrum we have fixed length, repeating sprints. We bring work to the sprint, rather than creating sprints from tasks.
This is useful for a number of reasons, including:
After a while we get to know the capacity of a sprint.
We know at the start of the sprint what we will be doing and there is no change to the sprint goal during the sprint. This stability helps the team get organised.
The regular cadence helps the team get into a rhythm of planning, executing and then adapting.
Scrum isn't as effective if:
You don't have a team of 3-9 people
Work items and priorities change frequently and stable sprints are not possible
From your description, I wonder if Scrum is the best agile framework for your team.
Perhaps you might consider using Kanban?
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
So I'm hopelessly lost right now. I found an attractive bluetooth chip from Nordic Semiconductor (the NRF52840) that I want to use for a couple project ideas I have. Now I have an HC-05 module for my arduino, so I'm not entirely lost on programming a bluetooth module perse, but I really need advice on how I can make my own. I want to make a bluetooth module that works exactly like the HC-05 but on a much smaller scale. I'm talking fitbit small. I'm not making a smartwatch or fitbit, but that's relatively the size I would need it to be.
So bottom line to whoever got lost in that mumbling explanation of my hopelessness, I need some advice on how to develop my own Bluetooth module PCB. The onboard chip will be the aforementioned NRF52480. Thank you to anybody who helps!!
Given that you are endeavoring in a very complex task, I would recommend you to start from the reference designs provided by the chip manufacturer. They are very valuable, especially when dealing with RF.
See here and here, for example. About RF design, this talk may be interesting for you as well.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I just drew an activity diagram, and I have 14 actors in my case. (I am making an activity diagram of online shopping site.)
Anyway... I am facing a problem with it, I am curious whether I must draw all actors in my diagram.
I have few system actors, so I am confusing how I place those actors between normal actors and system actors.
There are seller, non-seller who only buy products, and a manager who checks product posts. And finally I have to draw shipping system, certifying credit system, and more.
Thank you.
Well, I would say your use case is cut the wrong way. If it involves 14 actors then it looks like a pot of spaghetti and you did not sort out well. Look at the use case and try to find out what is wrong. There should not be more than 3 actors involved.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
In Agile, should the 'user' in a user story always be the end-user or could it refer to different type of user? For example, is it acceptable to write something along the lines of, "As a developer I would like to have an interface to component B so that I can communicate with it from component A" or should it be restructured in terms of the benefit that such an interface would ultimately present to the end-user?
Chris,
The answer is "it depends on who the customer is". User stories need to be understandable and if possible written by your customer. If your customer is a developer of component A or B then it would make sense to you both.
However, if the customer doesn't immediately see the benefit of that I would ask "why" I was adding that interface and keep asking "why" until I get to an answer that the customer does understand. Then I'd write the user story so that the customer can understand what is being delivered.
Mike Cohen's book User Stories Applied is very good if you're looking for something more substantial to read.
http://www.amazon.co.uk/User-Stories-Applied-Development-Signature/dp/0321205685/ref=cm_rdp_product
Of course it is. If you are say writing a dll to develop with, then you are the end user of the dll...
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
Are user stories (typically used in agile development or test driven development) the same thing as events in Edward Yourdon's structured analysis methodology?
Events and user stories are related but not identical. A Yourdon event is any stimulus to the system that requires the system to respond, so, for example, a tick from an external clock could be an event. That might require a response, eg, by incrementing a counter, but it wouldn't necessarily lead to a result with direct business value to the customer, so wouldn't be a valid user story or use case.
A user story is a pattern for briefly describing a business, technical or other type of need.
For example:
As a risk analyst I would like to add references to the application page so that we can store the references with the application, where the verifications team can then use them to help improve our risk rate in our underwriting.
Then in your user story you would decompose the story describing what tasks will be needed to complete the "would like" with a "done" check point being the "so that".
Mike Cohn has a good article on User Stories and the advantage of them http://www.mountaingoatsoftware.com/articles/27-advantages-of-user-stories-for-requirements
As far as Edward Yourdon's structured analysis methodology, I have to admit I'm not extremely familiar with it so I cant answer that part of your question.
That´s right, user stories and use cases from UML are rewrites of Yourdon´s events. They are just a reinvention of the wheel.