In agile methodologies, the story point is used as a way to estimate the effort it would take to complete a piece of work. The inputs to estimate story points are the complexity of the task and the amount of times that the task must be executed.
During agile rituals (sometimes called meetings), the number of story points for a task is estimated by all the members of an agile team. The value of this estimation process is two fold.
Blockchain technology can help the C-suite implement robust digital systems that reduce fraud and increase data reliability. But preventing scandals is secondary to meeting revenue and EBIT targets. With enterprises still busy switching from paper to bytes (read digitization), the enterprise blockchain can use this phase to polish its technology and demonstrate its value added.
The user story is a great way to put yourself in the “user” seat and do a reality check for whether what you are planning to build is something the “user” really needs or wants. The user story formula goes
As a [user description]
I [want, need, wish] to [some goal]
so that [some benefit].
Though this formula appears simple, I often see it applied in the wrong way.
A hackathon is to coding what a marathon is to running. Hackathons bring together coders and designers to work on a problem, or challenge, and produce some result, usually presented in a pitch slam at the end of the event. I have completed three different hackathons with three different teams and won a total of four prizes with them. This post is about how my teams did it.
In a small business, it is often the case that a single employee can play a critical role in boosting (or sinking) the business’s brand. And so it is important that at every touchpoint a potential customer receives a consistent message. In today’s world we focus a lot on the digital realm but I want to explain how to do this across both the digital and analog worlds in a way that showcases a business’s values.