Axosoft is passionate about supporting our community through donations, sponsorships, volunteer work, mentorship, teaching, and really any other way we can think of! That’s why we’re excited to participate in Arizona Gives Day today!What is Arizona Gives Day?
Arizona Gives Day is a single statewide day of giving that has raised $4.5 million for Arizona nonprofits since 2013. This year, #AZGivesDay will take place on Tuesday, April 5, 2016 from 12:00 a.m. to 11:59 p.m. (Arizona Time).
Okay, but why is it important?
Arizona nonprofits provide necessary services to our communities and are actually an integral part of our state’s economy. Annually, they have an economic impact of $22.4 billion, or nearly 8% of Arizona’s gross state product, and employ 324,000 people.
So, what should we do?
Monetary donations are the most direct way to help a nonprofit make an impact! Donations empower nonprofits to allocate funds where they are most needed. Arizona Gives Day is focused on helping participating nonprofits raise funds that are critical to supporting their work.
At Axosoft, we’re donating to a nonprofit called Support My Club, whose mission is to help students on their path to graduation by engaging communities to fulfill the needs of school clubs and teams. Their vision is for all students to have the opportunity to pursue their hopes, dreams and aspirations through participation in extracurricular activities.
Support My club is able to meet their objectives through these donations! They have grown at a significant rate year-over-year since their inception in 2012; currently serving 83 high schools across the state of Arizona with nearly 400 clubs in Academics, Activities, Arts and Athletics. Donors have fulfilled over 4,200 needs totaling over $225,000!
According to Amy Armstrong, CEO and Founder of Support My Club,
“Research says that structured after-school activities work. They work to engage students, keep them in school, and keep them from participating in risky behaviors. Clubs and sporting activities need help to provide the inspired minds and innovative ideas of students with the tools to succeed in their missions. That’s where we come in.”The Story of Support My Club
I asked Amy what inspired her to found Support My Club, and this was her response:
“I was working with a local high school and saw the amazing talents and innovative ideas that these students had, but many were just dreaming about them because they didn’t have the tools or resources to make them come to life. For example, there was a newly formed Fashion Club with gorgeous sketches of ball gown, but they didn’t have a sewing machine, fabric, scissors or thread—so the ideas sat on paper. After we equipped them properly, they created an entire line of original dresses and held their first runway show! There were so many examples like that… opportunities for the students to pursue their talents and passions if they were supported.”
For Support My Club, Arizona Gives Day is an important day because it not only brings awareness to their services and opportunities but it is a chance to gather with other nonprofits in a day of celebration! Amy remarked,
“Nonprofit employees, board members and volunteers work very hard on a wide variety of issues in our state and I so appreciate the community feeling of support that is shown on Arizona Gives Day.”Get Involved!
Amy proudly told me,
“Last year, the money raised during this 1 day was what funded an AmeriCorps VISTA to be placed with us full time for 1 year. That capacity building position allowed us to open up our services statewide and we are now serving 7 additional counties outside of Maricopa!”Arizona Gives Day stats for 2015
Version 16.2 is here! We have a UX-focused release for you with several handy improvements. Here’s what you can expect:
- Quick Filter on multi-select lists
- Remaining Estimate update
- Standup burndown can now be filtered by team
- Multi-select options in Users section
- Work logs tab update
- Audit Trails rebuilt to track more changes.
Did you know you could quick filter on grid columns? The option is available when you right click on a column header in grid view:Hover over a column in grid view to use a quick filter.
Now we have expanded this quick filter to multi-select lists. Say you tag an item with several options in the your multi-select list. With this new feature set, you can filter down to a specific selection so you only see what you need. Yay filters!Remaining Estimate update
We made Axosoft a little smarter with this update. Select an item and then hit d on your keyboard.Use the keyboard shortcut “d” to modify durations.
Now any time both fields are blank when you open a new or existing item, Axosoft will update the Remaining Estimate field when you enter a value in the Initial Estimate field. It will even update as you update the Initial Estimate field. However, if you explicitly state a value for the Remaining Estimate field then Axosoft will respect that data entry moving forward.What’s new with the Stand Up
Teams filters for the Stand Up burndown charts are now available. Access this menu as shown below to enable your team filter:Get a burndown chart that only displays work by the selected team.
Now only items from members of the selected team will show in the burndown chart.What can I do with users now?
Did you know that you could right-click on a user when you navigate to Tools/ People/ Users?This menu can be accessed from Tools/ People/ Users
As of version 16.2, you can multi-select users and right-click to make bulk changes. Activate, deactivate, or unlock multiple users at once.What other multi-select options are new?
For up to 100 items at once, you can perform the following bulk actions on multi-selected items:
- Copying to other item types
- Move to other item types
Remember, when deciding between “Copy to” or “Move to” we always recommend defaulting to the copy option so you keep an original record.Where can I add a work log?
It is now even easier to add to your work logs for a specific item. Simply navigate to your work logs tab, and right-click on an existing record to log more work.Right click on a record to get this menu.
You can also use the keyboard shortcut W to add an additional work log for the selected record.More Audit Trails
We reworked the backend for Audit trails so that it tracks system changes to include:
- And more
For now, system changes are limited to name changes. Don’t forget, you can also include item audits in addition to any system object updates.
Lastly, we updated the Organize Panel and the Details Panel so that they fly open or close when you click the arrow icon. There is no need to pin any longer
The end of an agile sprint or iteration should be a relatively lightweight occasion. After all, it’s something that will be done at least once a month, and often much more frequently than that. So, it’s important that we don’t burden a team with any more process ceremony than necessary. Often a very simple sprint review is all that is needed.A Sprint Summary Document
Sometimes, though, as a ScrumMaster, I like to produce a sprint summary document. This short document contains very brief details of what work was done during the sprint, when the sprint was, who was on the team, any key decisions that were made during the sprint, and perhaps a few important metrics.Audience
There are two target audiences for a sprint summary document. The first is any interested outsiders. This could include the VP of development, executives, stakeholders, department management, other teams and so on.
The second audience is future versions of the agile team itself. I’ve been in many situations where a team wanted to look back in time. A sprint summary can provide that view. Let me provide an example.
This one team was feeling depressed about how few automated tests they were writing. In the prior sprint, they’d added only about 200 total automated tests, which they knew was too low for what their system needed.
Because their ScrumMaster had been producing sprint summary documents, I retrieved a summary from six months earlier.
I shared with the team that they had once been struggling to write even one or two automated tests per sprint. (They were refactoring code so that it could support automated testing and were learning the concepts and tools.)
By sharing this information with the team from their sprint summary, I helped them realize how far they had come. Yes, they still had a long way to go, but they had already started moving the mountain, and momentum was now on their side.
Without a sprint summary document to provide exact facts, I would have had to rely on memory or had to piece things together by digging through the source code repository.Content
While the specific contents of a sprint summary document are entirely up to you, there are a few things I’ve found to be helpful. These include ...Context
Simply list the start and end date of the sprint and the number of working days in the sprint. I also list the people who were on the team, how many days each was expected to be available and the approximate number of days each was actually available.
The number of days a team member worked may differ from the planned days available because of illness or because the person was pulled onto another project mid-sprint, for example.Metrics
Include any metrics here that are important to the ScrumMaster, stakeholders or the team. Keep it simple. I tend to include a graph or table of the velocity of the last 10 or so sprints (whatever horizon seems reasonable for your team). If you’re using burndown charts, include those.
You might also consider including things like the number of defects found or fixed, the number of automated tests added, code coverage, the number of builds deployed and so on.
If you are building the software for a client and need to report on cost, include things like billable hours and cost in this section.
But keep it simple.Contents and Assessment
In this section, include a list of each product backlog item the team planned to do. Indicate whether the item was finished or not. And if the team estimates product backlog items (for example, in story points), include the size of the story.
Also include any additional notes from the sprint review on relevant decisions.
Finally, consider including a list of actions decided as a result of the sprint retrospective. This is entirely optional and be sure the team is OK including this. They may or may not be, depending on the audience for the sprint summary document.Keep The Effort Short
Once you’ve produced an initial sprint summary document, you should find creating a new one for each sprint quite simple. My guideline is that it should not take more than 15 minutes per sprint to produce. If you keep the metrics section simple, this is quite feasible.
I’ve included a sample sprint summary document you can use to get started.What Are You Tracking?
In the comments below, please share your thoughts. What do you think of the things I like to track? What do you track already? Or what will you begin tracking now after reading this?
VersionOne is excited to release the 10th annual State of Agile™ Report – one of the key ways that the company proactively gives back to the software development community. For more than 10 years, this annual survey has collected unbiased feedback to give software professionals insight into agile trends, best practices, and lessons learned to help them succeed with their agile transformations. In fact this year there were a total of 3,880 completed responses, of which only 28% were VersionOne customers, further adding to the range and diversity of respondents. While many of the trends remained constant, we were surprised by some of the results.
Here’s a sneak peek:
- Larger enterprises are embracing agile – 24% of respondents work for organizations with 20,000+ employees.
- Agile is scaling – Scrum still dominates, but the Scaled Agile Framework® (SAFe®) made a big jump this year.
- Agile talent and experience is growing – 63% said they were ‘very’ to ‘extremely’ knowledgeable about agile.
- Agile is going global – 26% of the respondents work in Europe, and more than 18% work in Asia, South America, Oceania, and Africa.
- You’re succeeding with agile – 95% reported that their organizations practice agile, and only 1% had experienced agile failure.
Read the report and get access to the archives of the previous nine State of Agile reports.
VersionOne is a registered trademark and State of Agile is a trademark of VersionOne Inc.
Scaled Agile Framework and SAFe are registered trademarks of Scaled Agile, Inc.
The post The Results Are In! Read the 10th Annual State of Agile Report appeared first on The Agile Management Blog.
NO and YES are two simple words, yet practice shows that professionals often have difficulties in using them. Actually it's very easy, certainly when you want to work in an agile way. Dare to say NO when you are unsure if you can do what's requested. When you say YES it means that you will deliver the product, on time with the right quality. Continue reading →
Do you have a question about doing agile retrospectives? Need some help on how to do them? I'm there to answer your questions. All you have to do is ask :-) Continue reading →
Last week, Sid Probstein, CTO of Attivio, and Andy Singleton, founder of Assembla presented a webinar about “Fast IT,” a new way of managing rapidly changing and Agile projects in areas like mobile, Web, analytics and marketing applications, while working smoothly with reliable core systems ("Core IT"). Andy discussed the dynamics of Fast IT, and Sid presented a case study of how Attivio spun up a major Business Intelligence app in two weeks with two people.
If you missed the webinar, view and download the slides.
Want an overview of Fast IT in 60 seconds? Watch the video below:
Get notified about new and exciting content around Fast IT by completing the form below:
Paying for your Assembla subscription with PayPal has never been easier. We recently added the ability to set up recurring payments with PayPal that will automatically pay for your Assembla subscription every billing period, whether that be monthly or annually. Previously, it was a manual process that required logging in and paying every time an invoice was created.
To set up automatic payments with PayPal, visit your billing page > select the PayPal option > and follow the steps.
If you have any questions or issues, please contact Assembla support at firstname.lastname@example.org.
If your team uses Slack, HipChat, Flowdock, or Bigplans for communication, we have added preconfigured webhooks to make setting up these integrations painless. Once configured, you can selectively manage the Assembla events that are posted out to these apps, such as ticket activity, commits, deploys, etc., to monitor project activity in real-time, inline with other team communication.To get started, click on the desired integration below:
Ripple is a protocol for value exchange that makes it easy to transfer and trade fiat currencies, Bitcoin, or XRP - the native asset of the Ripple network.
Assembla is giving away 1000 free XRP (the Ripple native cyptocurrency) to any person with software development skills who is interested in learning about Ripple development. Get it here: https://www.assembla.com/ripple
I called Ripple Labs a few months ago to find out more about ways that their "gateway" can help us pay developers in many different countries. Essentially, we do banking for the developers on our global team. We pay internal accounts, hold the money until they ask for it, and then transfer money to them by bank wire, ATM/Payoneer, or other mechanisms. We have found that the bank wire system is embarrassingly slow and unreliable. This is the problem that Ripple is trying to fix. Their gateway is like a bank in an open-source box. It keeps accounts in any currency, including USD, other currencies, XRP, and Bitcoin. It can transfer those accounts instantly and reliably on the shared "ledger." It is also gaining exciting new features such as "multi-signature" which enables outsourcing and crowdsourcing customers to post a budget amount, and then transfer it to their hard-working suppliers through an arbitrator.
Now I am working more closely with Ripple to help them scale up their development process. I decided to make this free XRP offer for two reasons:
- Users need 20 XRP to activate a Ripple wallet. We want to remove the hassle from acquiring the XRP so new developers can get started.
- We want to build an email list of developers that might be interested in working on internal development, bounties, or bank integration projects.
If you use Assembla and Bigplans, we have added a pre-configured webhook making it easy to post Assembla events out to your Bigplans chat room. Check out below for configuration instructions.
Bigplans is a simple, integrated way to manage a distributed team. It includes a "lean" task board, real-time chat, and a unique "advisor" (a real person) that helps you get on-demand resources if you need them. For programming teams, it includes a tight integration with Assembla login and Assembla tickets.
You can use the Webhooks tool to feed Assembla events into any of your team chats. To get started, you will need the Webhook tool installed in the Assembla project you want to configure. If you do not have the Webhook tool installed, visit the Admin tab > Tools section > and click ‘Add’ next to the Webhook tool.
Once installed, click on the Webhook tool in your main navigation and select Bigplans from the list of pre-configured post options:
You will need to obtain and update the auth token in the “Content” section.
To obtain your Bigplans auth token:
Visit Bigplans and navigate to the plan you want to post Assembla events to. Click on the ‘Connect’ option in the top bar. Under the “Message API” section, there is a section called “API Token” that will display your token. If no token is set, click on the ‘Reset’ button. Copy the token ID and replace the “BIGPLANS_AUTH_TOKEN” in the Webhook tool.
Now configure what Assembla events you would like to post to your Bigplans chat room and click ‘Add and Authenticate.” Don’t forget to enable the configuration under the “Title” field.
Your Assembla events will now be posted to the configured Bigplans chat room:
If you use Assembla and Slack, we have added a pre-configured webhook making it easy to post Assembla events out to your Slack chat room/channel. Check out below for configuration instructions.
To get started, you will need the Webhook tool installed in the Assembla project you want to configure. If you do not have the Webhook tool installed, visit the Admin tab > Tools section > and click ‘Add’ next to the Webhook tool.
Once installed, click on the Webhook tool in your main navigation and select Slack from the list of pre-configured post options:
You will need to setup an incoming webhook service integration within Slack to obtain your token. To do this, visit https://YourSubdomain.slack.com/services/new/incoming-webhook, select the desired channel to post to, and click ‘Add Incoming Webhook.’
Once created, copy the provided Webhook URL and update the External URL in Assembla’s Webhook tool.
Now configure what Assembla events you would like to post to your Slack room/channel and click ‘Add and Authenticate.' Don’t forget to enable the configuration under the “Title” field.
Tip: Within the Slack “Incoming Webhook” page that you set up for this integration, you can scroll to the bottom of the page and expand the “Integration Settings” where you can add a label, change the post-to channel, and change the icon and name for your webhook bot.
Your Assembla events will now be posted to the configured Slack room/channel:
If you use Assembla and HipChat, we have added a pre-configured webhook making it easy to post Assembla events out to your HipChat chat room. Check out below for configuration instructions.
To get started, you will need the Webhook tool installed in the Assembla project you want to configure. If you do not have the Webhook tool installed, visit the Admin tab > Tools section > and click ‘Add’ next to the Webhook tool.
Once installed, click on the Webhook tool in your main navigation and select HipChat from the list of pre-configured post options:
You will need to obtain and update the auth token and room ID in the “Content” section.
To obtain your HipChat auth token:
You will need to visit https://YourSubdomain.hipchat.com/admin/api and enter your password to access the “API Auth Tokens” page. Under “Create new token” select ‘Notification’ type, provide a label, and click ‘Create.’ Copy the token ID and replace the “HIPCHAT_AUTH_TOKEN” in the Webhook tool.
To obtain your HipChat room ID:
Visit https://YourSubdomain.hipchat.com/admin/rooms and click on the desired room you would like to post Assembla events to. Copy the App ID and replace the “HIPCHAT_ROOM_ID” in the Webhook tool.
Now configure what Assembla events you would like to post to your HipChat room and click ‘Add and Authenticate.” Don’t forget to enable the configuration under the “Title” field.
Your Assembla events will now be posted to the configured HipChat room:
When we at Assembla heard about the 2-2-2 project structure used by Attivio, we knew we had a fun story and a big idea to share. The fun story is the way that Attivio can spin-up major Business Intelligence apps with 2-day, 2-person prototyping sessions. The big idea is “Fast IT”: a way of managing fast and Agile projects, while working smoothly with your slower, more reliable core systems: "Core IT".
In this Webinar, Sid Probstein, CTO of Attivio, and Andy Singleton, founder of Assembla, will share their discoveries about ways that “Core” and “Fast” can work smoothly together. We will show tools that help you wrap and index your Core IT so that you can easily use it in Fast IT projects. And, we’ll show how to professionally launch and manage an expanding portfolio of Fast IT projects for analytics, Web, mobile and marketing applications and SaaS integration.
This Webinar is designed to help IT professionals or project managers who are handling analytics, Web, mobile, cloud and marketing applications.
Garrigan Lyman Group was worried about losing the loyalty of its own customers. The agency was expanding rapidly and tackling more complex e-commerce, mobile, social media and video projects. Clients had no visibility into when new requests would be delivered. Development managers were having trouble tracking releases and matching resources to requirements. Teams needed a solution to prevent missing deadlines and ensure the quality of delivery.Objective
Chris “Whitey” Geiser, GLG’s CTO, knew that the agency could not afford to lose “customer equity,” the hard-won confidence that GLG could deliver innovative digital marketing solutions. So he and his team began looking for technologies that could help them centralize processes, manage development requests, and improve communications with clients.Results
Assembla has helped Garrigan Lyman Group win new business from existing clients. The solution has helped GLG evolve from helping clients with flashy but self-contained marketing projects, to solutions that work with the core of their businesses. It allows the company to collaborate better with clients and improve control of their development processes.
To see how GLG learned to work more closely with its customers,
fill out the form below to download the full case study.
Scrum.org announced today that its Chief Craftsman, David Starr, will soon be joining Microsoft as Senior Program Manager in Visual Studio ALM.
Since joining Scrum.org in 2011, David has driven significant improvements in all of Scrum.org’s programs, and has dedicated himself to helping teams around the world improve their software development. David is leaving his post as Chief Craftsman for Scrum.org to help Microsoft continue improving Visual Studio to support agile software development practices.
In discussing his new role David said, “There is a saying that the tool sets the rules. As unfortunate as that statement is, it is true for many organizations who don’t yet value people over process and process over tools. I look forward to delivering products that encourage good agile practices with a focus on better people interactions and higher quality software. Creating features for a product that is used by millions of software developers is humbling.”
"It is with mixed emotions that we bid David farewell," said Alex Armstrong, Scrum.org's co-founder and VP of Business Development. "David has made incredible contributions through his work at Scrum.org, and we will miss him at each and every Daily Scrum. As part of the Scrum.org team, David has been directly helping to improve the profession of software development. We are excited that he will be able to continue to do so with a company as central in the software development universe as Microsoft," Armstrong continued.
“I have been privileged to work with the thought leaders at Scrum.org. The Professional Scrum Trainers and others in the Scrum community are some of the most committed and talented people contributing to our craft,” said Starr.
“I will miss my interactions, heated discussions, and finally resolutions with David.,” said Scrum.org founder Ken Schwaber. David drives integrity, and that is essential to Scrum.org’s mission and to the well-being of our profession.
Asked about the significance of Microsoft’s choice, Armstrong summarized, ”By bringing a Scrum practitioner with David's unique mix of talents into a leadership role on its flagship ALM product, Microsoft is clearly telegraphing its commitment to supporting Agile and Scrum teams. Agile’s influence in software development has been increasing steadily over the past decade, and this seems to be a clear demonstration of the trend continuing.”
You can read more about David’s future plans on his blog.
It's a new month, and now there is a new Scrumy feature for Pro users: The Scrumy API. Pretty much anyone who has asked us if we have an API recently has already been directed to that page and has been able to access it, but now we're sharing our secrets with the world.
For the uninitiated, an API is an interface that we give to you in order to access the data that we've stored for you in a convenient way. Essentially, it allows you to write your own programs that interact with your Scrumy projects. If, for example, you wanted a big red button that moves all your unfinished tasks into the 'Done' column, you could build that yourself with a few clever API calls.
The Scrumy API is divided into two separate parts: REST and Webhooks.
The REST API allows you to get data from your projects in XML or JSON form using simple URLs. You can also manipulate your data by POSTing or PUTing data to those URLs. You can read all about it at the REST API documentation page.
Webhooks are very different. A Webhook is a URL for an application that you have running on your own server which receives data from us. This means that any time you create or change a task, for example, we will send a piece of data representing the change on your project to that URL. A simple thing you could do with this would be to send a tweet any time you finish a task. Read more at the Webhooks documentation page. Also, the demo is set up to use webhooks, but it works a bit differently than your projects. The demo will allow you to enter 5 webhooks, but none of them will be active for more than 5 minutes. So, if you just want to see how webhooks work, feel free to use the demo, but unless you want to be a jerk, use an empty slot. Then you have 5 minutes to test your heart out.
So those are the big updates for now. If you find errors while reading the apidocs or feel that you could clarify something, feel free to update the documentation. It's a wiki for a reason. If you have any other questions or comments, feel free to contact us at email@example.com.